Skip to main content
Glama
Sign In
rest_api_mcp

rest_api_mcp

by Muhammed-AbdelGhany
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fetch_spec

Retrieve the OpenAPI/Swagger JSON specification to discover API endpoints, HTTP methods, and request schemas for making API calls.

Instructions

Fetches the OpenAPI/Swagger JSON spec for this API. Use this to discover endpoint paths, HTTP methods, and request body schemas before calling request().

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

Input Schema

NameRequiredDescriptionDefault
urlNoOverride the spec URL. If omitted, uses API_SWAGGER_URL env var.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It describes the tool's behavior (fetching a spec for discovery), but lacks details on error handling, rate limits, or authentication needs. It adds some context about the default URL source but doesn't fully compensate for the lack of 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 front-loaded with the core purpose, uses two concise sentences with zero waste, and efficiently communicates key usage information without unnecessary details.

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 tool's low complexity (1 optional parameter, no output schema), the description is mostly complete for its purpose. However, it could benefit from mentioning the output format (JSON) or potential errors, slightly limiting completeness for a discovery 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?

Schema description coverage is 100%, so the schema already documents the single parameter. The description adds no additional parameter semantics beyond what the schema provides, such as format examples or usage nuances, meeting 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?

The description clearly states the specific action ('Fetches') and resource ('OpenAPI/Swagger JSON spec for this API'), and distinguishes it from sibling tools by explicitly mentioning its role in discovering endpoint information before using the 'request()' tool.

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

Usage Guidelines5/5

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

It provides explicit guidance on when to use this tool ('before calling request()') and implies an alternative (using 'request()' directly), with clear context about its purpose for API discovery.

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