Fetch any public http(s) URL and return HTML-stripped plain text, enabling easy reading of pages, docs, and blog posts.
Fetch a public http(s) URL and return readable plain text (HTML stripped). Use for pages, docs, blog posts.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Absolute http(s) URL to fetch | |
| max_chars | No | Max characters to return (default 8000) |
Changes observed during successful MCP inspections.
v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description is the only behavioral disclosure. It does disclose that only public URLs are fetched and that HTML is stripped into plain text, but it omits behavior around HTTP errors, redirects, timeouts, or response failure cases.
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 concise sentences put the core behavior first and the intended use cases second, with no filler.
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 two-parameter fetch tool, the description covers the main facts needed for selection and invocation: public URL input, plain-text output, and common use cases. It lacks error and redirect behavior, but the essential information is present.
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 coverage is 100%, so the description's parameter contribution is minimal and the schema already documents url and max_chars adequately. The description adds no extra parameter-level detail beyond that baseline.
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?
Description states a clear verb and resource with a specific transformation: fetch a public http(s) URL and return readable plain text with HTML stripped. The intended content types (pages, docs, blog posts) also help distinguish this from the fetch_json sibling.
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 gives clear positive context for when to use this tool: for pages, docs, and blog posts. However, it does not explicitly contrast it with fetch_json or state when NOT to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.