Skip to main content
Glama
Rekl0w

MCP OpenAPI Discovery

by Rekl0w

call_endpoint

Execute HTTP requests against any OpenAPI endpoint with automatic authentication, path, query, header, and body parameters.

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. It mentions optional auth but fails to disclose error handling, idempotency, or mutual exclusivity of body and rawBody. The description is too brief for a tool with 11 parameters.

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 of 25 words, which is concise and front-loaded. However, it could benefit from a brief second sentence about auth usage or parameter relationships.

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?

Despite the complex input schema with 11 parameters, nested objects, and no output schema, the description is minimal. It doesn't explain that the url can be a docs page, that body and rawBody are alternatives, or that path params are required. The description is incomplete for the tool's complexity.

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?

All parameters have schema descriptions covering 100%, so the baseline is 3. The description adds value by mentioning automatic auth, but overall it does not significantly enhance the schema's clarity.

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 action: calling an endpoint from an OpenAPI document. It includes key features like automatic auth and data sending. It distinguishes from sibling tools that deal with detection and listing, not actual calling.

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?

Usage is implied: you call an endpoint after discovery. No explicit when-to-use or when-not-to-use. No alternatives are mentioned. The description assumes the agent knows this is the main execution tool.

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