Category guide
AI Developer Tools
Function tools connect an AI model to code that your application controls. A definition can be valid JSON yet still have the wrong provider wrapper or an unusable argument schema. Check one tool definition locally, compare the output with current provider docs, then test a complete request against the API.
Choose the right tool
OpenAI Tool Schema Validator
Use this checker for one OpenAI Responses function tool and its common strict-mode object rules.
Claude Tool Schema Validator
Use this checker for one Claude client tool with a name, description, and input_schema object.
AI Tool Schema Converter
Use the converter when moving the shared name, description, and argument schema between provider wrappers.
All tools
Example workflow: move a lookup function between providers
- Start with one working tool definition and validate its JSON shape with the checker for its current provider.
- Convert the definition to the other provider's wrapper and inspect the required fields and nested object schemas.
- Run the destination checker, then test the complete request with the current API and your application's argument validation.
Before you use the result
These pages check or map a limited structural subset. They do not contact a provider, execute a function, or guarantee that a model or API version accepts every schema keyword. Review strict-mode changes to optional fields before using converted output.
Shape checks before API tests
The OpenAI tool schema checker expects a single Responses function tool object. The Claude tool schema checker expects a single client tool. Both catch basic wrapper and object-schema mistakes locally. Neither evaluates whether a description leads to the right tool choice or whether your application handles arguments safely.
Provider documentation changes, so treat the page result as an early check. Confirm the final request against the current OpenAI function calling guide or Claude tool guide, and run an integration test for the model and API version you use.
Conversion deserves a manual review
The AI Tool Schema Converter maps the common wrapper fields. Optional fields need attention when converting to a strict OpenAI schema: normalization can make a property required while allowing a null value. When converting back, a required nullable field does not reveal whether it was originally optional. Compare a sample function call with the receiving function’s actual argument handling before deploying the definition. Tool definitions stay in the browser during these checks.