Swagger MCP Adapter

get_all_service_information

Retrieve detailed info on all API services from a Swagger/OpenAPI spec, including parameters, request/response schemas, and examples.

Instructions

Get detailed information about all API services from a Swagger/OpenAPI specification including parameters, request/response schemas, and examples

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": {
      "swaggerUrl": "<swaggerUrl>"
    },
    "name": "get_all_service_information"
  }
}

Input Schema

Name	Required	Description	Default
`swaggerUrl`	Yes	URL of the Swagger/OpenAPI specification to load and analyze

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 1, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, the description conveys the read-only intent through 'Get' and lists the kind of data returned (parameters, schemas, examples). However, it does not disclose whether fetching the spec may have side effects, network requirements, or error behaviors.

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, well-structured sentence that front-loads the purpose and includes relevant output content details without any fluff.

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

Completeness4/5

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

Given the simple one-parameter input and no output schema, the description provides sufficient context by stating what information is returned. It also differentiates from sibling tools, though it could mention the read-only nature or behavior when the URL is invalid.

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?

The single parameter swaggerUrl is fully described in the schema (100% coverage). The description adds no extra detail about parameter format or constraints, aligning with the baseline for high schema coverage.

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?

Description clearly specifies the verb 'Get' and the resource: detailed information about all API services from a Swagger/OpenAPI spec. The inclusion of 'all' distinguishes it from the sibling tool get_service_information, and the detail level separates it from list_services.

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

Usage Guidelines3/5

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

The description implies use for retrieving comprehensive data on every service in a spec, but it does not explicitly state when to use this over get_service_information or list_services. No alternatives or exclusions are mentioned.

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

Deploy Server