MCP OpenAPI Discovery
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| detect_openapiB | Given a docs or API URL, detect the OpenAPI/Swagger document behind it and summarize the API structure. |
| list_endpointsA | List endpoints from a discovered OpenAPI document with optional filtering by tag, method, or path fragment. |
| search_endpointsB | Search cached endpoints for a previously detected OpenAPI spec using a server-side semantic-style scorer over endpoint metadata and schema field names. |
| suggest_call_sequenceA | Suggest a likely API call sequence for reaching a target endpoint or accomplishing a goal, such as creating prerequisites before creating a dependent resource. |
| get_endpoint_detailsC | Return request/response details for a specific endpoint in the discovered OpenAPI document. |
| call_endpointB | Call an endpoint discovered from the OpenAPI document, optionally applying auth automatically and sending query, path, headers, and payload data. |
| trace_parameter_usageB | Trace where a parameter or field such as userId is used across path parameters, query parameters, request bodies, and response bodies. |
| find_related_endpointsB | Find endpoints that are structurally related to a source endpoint based on shared resource paths, identifiers, tags, and parent/child URL patterns. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Most tools have clearly distinct purposes, though search_endpoints and list_endpoints could be confused due to both listing endpoints; however, their descriptions differentiate search vs. filtering.
All tool names follow a consistent verb_noun pattern (e.g., call_endpoint, detect_openapi), making them predictable and easy to distinguish.
8 tools is well within the optimal range (3-15) and covers the core workflow of OpenAPI discovery and interaction without being excessive.
The tool set fully covers the lifecycle: detect, list, get details, call, and includes advanced features like semantic search, relationship discovery, sequencing, and parameter tracing.