get_endpointComplete documentation for one endpoint of a marketplace API: parameters with types and requirements, request body, documented responses with examples, and billing.
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | The endpoint path exactly as listed by get_api, e.g. /v1/search. | |
| slug | Yes | The API's marketplace slug. | |
| method | Yes | HTTP method, e.g. GET or POST. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must convey the tool's behavior. It explains what the returned documentation covers (parameters, request body, responses, billing), but does not explicitly state that it is read-only or mention potential side effects or authorization requirements. The 'documentation' wording strongly implies read-only, but the absence of explicit disclosure is a minor gap.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, information-rich sentence that front-loads the tool's purpose and lists its key outputs without wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema, the description sufficiently outlines the return content (parameters, request body, responses, billing). It is complete for a low-complexity documentation tool and aligns with sibling tools like call_endpoint, though it does not mention error behavior or prerequisite actions.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema already provides 100% coverage of the three parameters with clear descriptions, so the description adds no extra parameter-level detail. This meets the baseline of 3 for well-covered schemas.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('get') and resource ('endpoint documentation'), and clarifies that it covers one endpoint, distinguishing it from siblings like get_api (which likely lists endpoints) and call_endpoint (which invokes them).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase 'for one endpoint of a marketplace API' clearly implies use when full details about a specific endpoint are needed, which differentiates it from listing all APIs or searching. It does not explicitly state when not to use it, but the context is clear enough.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clear, non-overlapping purpose: one searches for APIs, two provide metadata (overview vs. endpoint docs), and one executes calls. The distinction between get_api and get_endpoint is well defined by scope (API-level vs endpoint-level).
The naming follows a consistent verb_noun pattern (call_endpoint, get_api, get_endpoint, search_apis) with only minor deviation: 'search' instead of 'get' for the search tool, which is conventional. The pattern is clear and predictable.
With only 4 tools, the set is tightly scoped to the marketplace's purpose: discovering, documenting, and executing APIs. Each tool is essential for the core workflow, and 4 is a reasonable number for this domain.
The surface covers the main lifecycle: search to find, get_api to understand, get_endpoint for details, call_endpoint to execute. Missing features like authentication management or plan/subscription management are external to the core usage, so this is a minor gap.