Skip to main content
Glama
Rekl0w

MCP OpenAPI Discovery

by Rekl0w

call_endpoint

Call an API endpoint using its OpenAPI specification, with support for path, query, headers, body, and automatic authentication.

Instructions

Call an endpoint discovered from the OpenAPI document, optionally applying auth automatically and sending query, path, headers, and payload data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesDocs page URL or direct OpenAPI JSON/YAML URL
methodYesHTTP method
pathYesExact OpenAPI path, e.g. /users/{id}
pathParamsNoPath template values, e.g. {"id":"42"}
queryNoQuery string parameters as an object or raw string, e.g. {"page":2} or "page=2&sort=name"
headersNoAdditional request headers
bodyNoRequest payload for JSON, form, or multipart requests
rawBodyNoRaw string body to send as-is
contentTypeNoOverride request content-type
timeoutMsNoRequest timeout in milliseconds
authNoAuthentication configuration
Behavior2/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 of behavioral disclosure. It mentions optional automatic auth and sending of various data types, but it lacks critical details: error handling, response behavior, idempotency, throttling consequences, or what happens on auth failure. For a tool with 11 parameters and nested auth objects, this is insufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence that captures the core action without redundancy. However, for a tool with complex inputs and behaviors, a second sentence on response or error handling would be beneficial without harming conciseness.

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

Completeness2/5

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

Given the complexity (11 parameters, nested auth object, no output schema), the description is incomplete. It does not explain the output structure, error conditions, or how to handle responses. The schema covers parameters, but the description should provide higher-level context that is missing.

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 input schema has 100% description coverage, so each parameter is already documented in the schema. The description ('sending query, path, headers, and payload data') aligns with the schema but does not add new meaning beyond what the schema provides. Baseline 3 is appropriate.

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 tool's purpose: 'Call an endpoint discovered from the OpenAPI document'. It specifies the verb 'call', the resource 'endpoint', and the source 'OpenAPI document'. This distinguishes it from sibling tools that focus on discovery (list_endpoints, search_endpoints, etc.) rather than execution.

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 after OpenAPI document discovery (calls an endpoint 'discovered from the OpenAPI document'), but does not explicitly state when to use this tool versus alternatives like detect_openapi or list_endpoints. No exclusions or prerequisites are mentioned. The sibling context helps but is not part of the description.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Rekl0w/mcp-openapi-discovery'

If you have feedback or need assistance with the MCP directory API, please join our Discord server