Fetch one Agent Connectors listing by slug to inspect connector details without running or testing that server.
Fetch one Agent Connectors listing by slug. This does not run or test that server.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Listing slug, such as firecrawl. |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden and does well: it discloses the read-only nature and, crucially, the negative behavior that this does not run or test the server. It lacks disclosure of error/not-found behavior or auth requirements, so not a full 5.
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?
Two tight sentences, zero filler, with the scoping clarification front-loaded right after the core purpose.
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?
For a simple single-param lookup with no output schema, the description is nearly complete. It could mention what happens on a miss or that auth is required, but given schema richness it is adequate.
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?
Only one parameter and schema coverage is 100% with an example ('firecrawl') in the schema. The description adds nothing beyond the schema, so baseline 3 applies.
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?
States a specific verb (Fetch) and resource (one Agent Connectors listing) with the lookup key (slug). The clause 'This does not run or test that server' sharply distinguishes it from any execution-oriented neighbor.
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?
Clearly establishes this is a read-only lookup by slug and rules out the action of running/testing the server. No explicit routing to siblings (search_tools, list_categories), but the disambiguation from execution is a strong usage cue.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.