Skip to main content
Glama

Action2MCP Custom GPT Action to Remote MCP Compiler

convert_openapi_to_mcp

Compile an OpenAI Custom GPT OpenAPI 3.0/3.1 JSON or YAML Action schema into MCP tools/list definitions, SKILL.md, and Cloudflare Worker migration code before the Dec 11, 2026 retirement.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "convert_openapi_to_mcp"
  }
}

Input Schema

NameRequiredDescriptionDefault
schemaNoRaw OpenAPI 3.0/3.1 JSON or YAML string
auth_typeNoauto
schema_urlNoOptional public URL to openapi.json or openapi.yaml
instructionsNoOptional Custom GPT system instructions for SKILL.md

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full behavioral burden. It discloses the transformation and the output artifacts, but it does not say whether results are returned as text or written to files, nor does it mention auth requirements, rate limits, or side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single front-loaded sentence with no wasted wording. It states the action, input, outputs, and deadline efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has four parameters, no annotations, and no output schema, so the description should do more to explain invocation and return behavior. It lists the output artifacts but omits the return format and does not clarify whether schema or schema_url is required or how auth_type and instructions affect the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 75%, so the schema already documents most parameters. The description adds only general meaning about the OpenAPI input and does not explain auth_type, instructions, or how schema and schema_url relate, so it does not meaningfully exceed the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb, "Compile," and names the exact input resource: an OpenAI Custom GPT OpenAPI 3.0/3.1 JSON or YAML Action schema. It also names the concrete outputs, so the tool's purpose is immediately clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase "before the Dec 11, 2026 retirement" gives a clear migration context for when to use the tool. It does not state explicit exclusions or alternatives, but no sibling tools are provided and the usage context is still clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.