Generic tool to fetch content from any absolute URL, respecting robots.txt rules. Use this to retrieve referenced urls (absolute urls) that were mentioned in previously fetched documentation.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | The URL of the document or page to fetch |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the behavioral burden and does disclose that the tool respects robots.txt rules. However, it omits other important behavior such as authentication needs, redirect handling, rate limits, or what content format is returned.
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 short and front-loads the main purpose. The parenthetical '(absolute urls)' in the second sentence is slightly redundant with the first sentence, but the overall structure is efficient.
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 one-parameter fetch tool this is mostly adequate, and the schema fully documents the input. Since there is no output schema, the description should ideally say more about what is returned or how content is presented, which it currently does not.
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?
Schema description coverage is 100% for the single url parameter, so the schema already explains the parameter's meaning. The description adds the useful constraint that it must be an absolute URL, but provides no additional syntax or format details beyond that.
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 states a specific verb and resource: fetch content from an absolute URL. The word 'Generic' and the phrase 'any absolute URL' help distinguish it from the more specialized sibling fetch_rea_ghidra_docs, though no sibling is explicitly named.
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?
It clearly says to use this for referenced absolute URLs mentioned in previously fetched documentation. This gives an agent a concrete usage context, but it does not explicitly state when to prefer the sibling fetch_rea_ghidra_docs tool instead.
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.