apidog-mcp

apidog_patch_openapi

Apply RFC 6902 JSON Patch to an OpenAPI export, validate the patched spec, then import it into Apidog.

Instructions

Apply RFC 6902 JSON Patch to exported OpenAPI, validate, then import.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "patch": "<patch>"
    },
    "name": "apidog_patch_openapi"
  }
}

Input Schema

Name	Required	Description	Default
`patch`	Yes
`options`	No
`branchId`	No	Optional Apidog branch ID. Falls back to apidog.json.
`moduleId`	No
`projectId`	No	Apidog project ID. Falls back to apidog.json.
`oasVersion`	No		3.1
`exportFormat`	No		JSON
`environmentIds`	No
`addFoldersToTags`	No
`includeApidogExtensionProperties`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.1Jul 31, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, so the description carries the burden of disclosing side effects. It states the sequence 'validate, then import' which is a useful behavioral detail, but it does not mention that importing may overwrite existing endpoints or resources, nor any prerequisites like project configuration. The schema options (e.g., deleteUnmatchedResources, OVERWRITE_EXISTING) hint at destructive behavior, but the description omits this.

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 sentence of 11 words, front-loading the core purpose. It contains no filler or redundant information, making it highly concise and well-structured.

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

Completeness2/5

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

The tool is complex with 10 parameters, nested options, and no output schema. The description is too minimal: it does not explain the full workflow (whether it exports the current spec or expects an input), prerequisites, potential side effects, or error behavior. The sparse description is inadequate for a tool of this complexity.

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

Parameters2/5

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

Schema description coverage is only 20% (only branchId and projectId have descriptions). The tool description mentions 'RFC 6902 JSON Patch', which gives context for the patch parameter, but it does not explain the many options (schemaOverwriteBehavior, endpointOverwriteBehavior, deleteUnmatchedResources, etc.). With low schema coverage, the description should compensate, but it does not.

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 clearly states the tool applies an RFC 6902 JSON Patch to exported OpenAPI, validates it, then imports it. It uses a specific verb ('Apply') and resource ('exported OpenAPI'), and the combined validate-import sequence distinguishes it from sibling tools like apidog_validate_openapi and apidog_import_openapi.

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 description implies the tool is for patching an exported OpenAPI and then importing it, which gives clear context for when to use it. However, it does not explicitly contrast with using separate export, validate, and import tools, nor does it mention exclusions or prerequisites. It provides just enough context to infer usage.

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

Deploy Server