T06 / LOCAL WORKBENCHNO ACCOUNT
LLM and MCP tool schema compiler
Compile a canonical JSON tool contract for OpenAI strict tools, Anthropic, Gemini, MCP 2025-11-25, or the MCP 2026 release candidate.
- Input
- JSON Schema or provider tool wrapper
- Output
- Target JSON, path diagnostics, repairs, and lossy-transform notes
$.inputSchemaClose this objectOpenAI strict requires additionalProperties: false on every object.
$.inputSchemaRequired array is incompleteStrict mode requires every property in required. APITC will make account_id nullable.
OPERATING NOTES01–03
What this tool checks—and what it does not.
- Local analysis
The supplied value is processed in the active tab. Remote endpoint behavior is not inferred when the evidence does not contain it.
- Evidence before advice
The report separates observed fields from implementation guidance. Preserve request IDs and provider error codes for production incidents.
- Version-aware verification
Provider behavior changes. Each related field note links to the official source used for the current rule.
THE RULES BEHIND THIS TOOL03 NOTES
Why it decided that.
Each note states the rule this workbench applies and cites the provider or standards document it came from.
Convert JSON Schema to an OpenAI strict function tool with recursive required and additionalProperties repairs.
Read the note →Interactive converterOpenAI to Anthropic tool schema converterTranslate an OpenAI function tool to Claude strict tool use while preserving optional-field intent.
Read the note →OpenAI schema errorFix “additionalProperties is required to be supplied and to be false”Diagnose and repair OpenAI strict tool schemas missing additionalProperties: false, including nested objects.
Read the note →FAQ
About this workbench
Does the tool schema compiler upload my data?
No. The value you supply is parsed and evaluated in the active browser tab. No account is required and no remote endpoint is called on your behalf.
What does this tool read, and what does it return?
It reads json schema or provider tool wrapper, and returns target json, path diagnostics, repairs, and lossy-transform notes.
How current are the rules it applies?
Each rule links to the field note that cites its primary provider or standards source, with the review date shown on that note. Provider behaviour changes, so verify against your pinned version before deploying.