get-endpointGets detailed information about a specific API endpoint, including security schemes and servers
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | The API endpoint path (e.g. /api/v1/users). | |
| method | Yes | The HTTP method (e.g. GET, POST, PUT, DELETE). |
| Name | Required | Description | Default |
|---|---|---|---|
| path | No | ||
| method | No | ||
| operation | No |
Changes observed during successful MCP inspections.
Output schema / (root)Previous value: -nullNew value: +{
+ "additionalProperties": true,
+ "properties": {
+ "method": {
+ "type": "string"
+ },
+ "operation": {
+ "additionalProperties": true,
+ "type": "object"
+ },
+ "path": {
+ "type": "string"
+ }
+ },
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds value by specifying that the response includes security schemes and servers, which is behavioral information about the output. There is no contradiction; the description aligns with the read-only nature.
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, efficient sentence that front-loads the purpose and includes the most relevant output aspects. No wasted words, and it avoids redundancy with the schema or annotations.
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?
The tool is a simple getter with a clear output schema (has_output_schema=true), so return values are already defined. The description covers the essential purpose and key output content. It could be improved by explicitly mentioning that this is for a single endpoint, but that is implied. Given the schema and annotations, it is sufficiently complete.
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 has 100% description coverage for both parameters (path and method), so the schema already fully documents them. The description adds no new syntactic or semantic detail beyond what the schema provides. Per the rubric, with high coverage, a baseline of 3 is appropriate.
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 clearly states a specific verb ('gets'), a resource ('detailed information about a specific API endpoint'), and names two concrete content aspects ('security schemes and servers'). This distinguishes it from siblings like list-endpoints (which lists all) and search-endpoints (which searches), making the tool's role unambiguous.
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 description implies the appropriate use case: retrieve details for one known endpoint (path+method). It does not explicitly mention alternatives or exclusions, but the wording 'specific API endpoint' signals when to choose this over list or search tools. Given sibling names in context, the agent can infer the distinction, though explicit guidance would be stronger.
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.