Swagger MCP Adapter

get_service_information

Retrieve comprehensive API service information including parameters, request/response schemas, and example usage from a Swagger/OpenAPI specification.

Instructions

Get comprehensive information about a specific API service including parameters, request/response schemas, and example usage

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>",
      "serviceId": "<serviceId>"
    },
    "name": "get_service_information"
  }
}

Input Schema

Name	Required	Description	Default
`serviceId`	Yes	The ID of the service to get information about
`swaggerUrl`	Yes	URL of the Swagger/OpenAPI specification

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 1, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It implies a read-only operation via the verb 'Get' and indicates the type of content returned, but does not state authoritative details such as permissions required, potential side effects (though likely none), or return format specifics. This is adequate but not rich.

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 unnecessary words. It efficiently communicates the core purpose and scope without repetition.

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 description covers the tool's main output content but lacks usage guidance, prerequisites (e.g., needing a swaggerUrl from another source), and explicit return structure details. Given the absence of an output schema and annotations, the description is only minimally complete for an agent to confidently invoke the tool.

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?

Both parameters are fully described in the input schema (100% schema description coverage), so the description adds no additional meaning beyond what the schema already provides. The mention of 'including parameters' is redundant given the schema's thorough descriptions.

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 a specific verb ('Get') and resource ('comprehensive information about a specific API service'), listing the exact content (parameters, request/response schemas, example usage). This distinguishes it from siblings like list_services (lists all services) and get_cache_information (focuses on cache details).

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It does not mention that this is for a single service while list_services is for all, or when get_all_service_information might be preferred. No exclusions or prerequisites are noted.

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

Deploy Server