CONTRACT DESK / CONVERT04 NOTES
One contract,
compiled per target.
Mechanical repairs where intent is recoverable; explicit warnings where it is not.
What this section covers
Moving a tool definition between providers is rarely a rename. The wrapper changes shape, optional fields change representation, unsupported keywords have to be dropped or emulated, and a construct that is idiomatic in one target may be unrepresentable in another.
Each conversion note documents the mapping in both directions, shows a before-and-after pair, and marks the transformations that change what the model can express — so a conversion is a decision you make, not a surprise you discover in production.
Tool schema converters
JSON Schema to OpenAI strict tool compiler
Convert JSON Schema to an OpenAI strict function tool with recursive required and additionalProperties repairs.
- Recursive strict repair
- Nullable optional fields
- Lossy keyword ledger
OpenAI to Anthropic tool schema converter
Translate an OpenAI function tool to Claude strict tool use while preserving optional-field intent.
- parameters → input_schema
- Optionality restored
- Complexity budget
OpenAI to Gemini function declaration converter
Compile OpenAI function tools into Gemini-compatible declarations and expose unsupported schema keywords.
- Tool wrapper conversion
- Nullable normalization
- Unsupported keyword report
MCP tool to OpenAI strict function converter
Convert MCP inputSchema tools to OpenAI strict functions and identify protocol semantics that do not carry over.
- inputSchema → parameters
- Recursive strict repair
- Annotation gap
RELATED WORKBENCHES01
Reproduce it locally.
These tools take the same evidence the notes above describe and compute the result in your browser tab.
Section FAQ
Before you dig in
What counts as a lossy conversion?
Any transformation that changes the set of accepted inputs or the meaning conveyed to the model: dropping an unsupported keyword, widening a constrained type, collapsing a union, or making a genuinely optional field required-but-nullable.
Do converted schemas still validate against the original?
Not necessarily, and that is the point of the warnings. A target-safe schema is valid for the target; whether it remains valid against your source contract depends on which repairs were applied.
CONTINUERELATED SECTIONS
Provider validators report a symptom at the root. The defect is usually several nodes deeper.
Open section →Contract deskProvider schema comparisonsField-level differences that change client code, not marketing feature tables.
Open section →Workbench indexAll six APITC toolsDecode, simulate, analyse, plan, diff, and compile — locally.
Open section →