Skip to main content
Glama
Sign In
swagger-mcp

swagger-mcp

by emreycolakoglu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List schemas

list_schemas
Read-only

List named component/definition schemas and their one-line descriptions from an OpenAPI/Swagger spec to identify data models at a glance.

Instructions

List named component/definition schemas with one-line descriptions.

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": "list_schemas"
  }
}

Input Schema

NameRequiredDescriptionDefault
specNoURL or local path of the OpenAPI/Swagger spec. Defaults to the server's configured API_DOCS_URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the description adds minor value by clarifying the output format (one-line descriptions). It does not mention any side effects, but none are expected. No contradictions with annotations.

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 zero wasted words. It efficiently conveys the tool's action and output form.

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?

Given no output schema and no annotations on pagination, the description does not explain whether the list is complete or paginated, nor the structure of the one-line descriptions. It is adequate for a simple list tool but leaves some ambiguity.

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 coverage is 100% and the schema already describes the single parameter 'spec'. The tool description adds no further explanation of parameter semantics, so it meets the baseline for high coverage without adding value.

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 verb 'List' and the resource 'named component/definition schemas', and specifies that it provides 'one-line descriptions', which distinguishes it from 'get_schema' (full detail) and 'search_schemas' (filtered).

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 usage for listing schemas but does not explicitly state when to use it versus alternatives like 'search_schemas' or 'get_schema'. No exclusions or when-not-to-use guidance is provided.

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

Deploy Server

Other Tools