>_
API

OpenAPI to LLM Tools

Convert an OpenAPI 3 or Swagger 2 spec (JSON or YAML) into tool definitions for OpenAI function calling, Anthropic Claude tool use or MCP servers. $refs are resolved and each endpoint becomes one tool.

Runs locally — your input never leaves this page.

Endpoints

    Output

    How to use

    1. Paste an OpenAPI 3.x or Swagger 2.0 document in JSON or YAML.
    2. Each operation becomes a tool. Path, query and header parameters and the JSON request body are merged into one input schema, and $refs are inlined.
    3. Untick endpoints you don’t want the model to call, choose the output format, and copy the tools array into your API request or MCP server.

    FAQ

    How are tool names chosen?

    The operationId is used when present. Otherwise a name is built from the method and path, such as get_users_by_id. Names are limited to 64 characters of letters, digits, _ and -, as LLM APIs require.

    Should I expose every endpoint as a tool?

    Usually not. Models choose tools more reliably from a short list with clear descriptions. Keep the endpoints the agent really needs and rewrite their descriptions to say when each one should be used.

    Report a bug or suggest a feature →