AI Developer Tools
AI Tool Schema Converter
Convert one user-defined Claude client tool shape to an OpenAI Responses function tool shape, or reverse that structural mapping.
✓ Every tool runs in your browser. We do not upload your input or output.
Keyboard shortcuts
Ctrl/⌘ + Enter: process
Ctrl/⌘ + Shift + F: full screen
Esc: exit full screen
Ctrl/⌘ + F in editor: search
How to use
- Paste one tool definition as JSON and choose the direction.
- Run the converter to map input_schema and parameters while preserving the name and description.
- For Claude to OpenAI, enable Strict OpenAI schema only when you want optional fields normalized to nullable required fields.
- Review the output with the related validator and test the final request against the current API.
Examples
Convert a lookup tool
The basic mapping preserves the schema while changing the provider-specific wrapper.
{"name":"lookup","description":"Look up a record","input_schema":{"type":"object","properties":{"id":{"type":"string"}},"required":["id"]}}An OpenAI function tool with parameters and strict: false
Move a tool definition between providers
Both provider formats describe a named function and its arguments with a JSON Schema object, but the wrapper fields differ. Claude uses input_schema; OpenAI Responses uses type: "function" and parameters. This converter maps the common name, description, and argument schema. It does not translate provider-specific tool settings or make API requests. One tool object is processed at a time.
For a Claude-to-OpenAI conversion, the default output sets strict: false so optional fields retain their original meaning. If you enable strict mode, the converter adds additionalProperties: false to object schemas, lists every property as required, and represents formerly optional values as nullable where it can. Review those changes carefully. A strict OpenAI schema may still be limited by the live API’s supported JSON Schema subset. The reverse direction preserves the OpenAI schema as written; it cannot know whether a required nullable field was intended as optional before normalization.
Use the related validators as an early shape check, then consult the OpenAI function calling guide and Claude tool guide before production use. The definition stays in your browser.
Frequently asked questions
Does this call either AI provider?
No. The definition is transformed locally in the browser.
What does strict normalization do?
It marks each object property required, disallows additional properties, and adds null to formerly optional property types where possible.
Can conversion preserve every provider feature?
No. Provider-specific metadata and schema limits need manual review.
What happens when converting strict OpenAI back to Claude?
Required nullable fields remain required; the converter cannot infer whether they were originally optional.