Interactive converter
MCP tool to OpenAI strict function converter
Convert MCP inputSchema tools to OpenAI strict functions and identify protocol semantics that do not carry over.
Input arguments translate cleanly only after strict repairs. MCP outputSchema and annotations have no direct OpenAI function-schema equivalent, so APITC reports them as contract-level portability gaps.
Read the schema and its provider wrapper as one contract. APITC distinguishes target requirements from portable JSON Schema, applies mechanical repairs only when intent is recoverable, and identifies transformations that can change meaning.
Diagnostic procedure
Repair the schema, then recompile.
- 01
Import the MCP tool
Paste a tools/list entry or a single tool definition.
- 02
Repair strict input
All objects are closed and optional fields become nullable-required.
- 03
Review lost protocol data
Keep output and side-effect semantics in your application layer.
{"name":"lookup","description":"Find a record","inputSchema":{"type":"object","properties":{"id":{"type":"string"}}}}{"type":"function","name":"lookup","description":"Find a record","parameters":{"type":"object","properties":{"id":{"type":["string","null"]}},"required":["id"],"additionalProperties":false},"strict":true}$.inputSchemaClose this objectOpenAI strict requires additionalProperties: false on every object.
$.inputSchemaRequired array is incompleteStrict mode requires every property in required. APITC will make limit nullable.
No account · no upload · no endpoint calledOpen the full tool schema compiler and operating notes →
FAQ
Before you ship
Does APITC upload my schema?
No. Parsing, diagnostics, and compilation run in your browser tab.
Is the compiled result guaranteed to preserve meaning?
Safe repairs are deterministic. When OpenAI cannot express a source constraint, APITC labels the transform as lossy instead of hiding it.
Protocol behavior checked against the OpenAI function calling guide. Recheck your pinned provider/API version before production deployment.