Fetch a public robots.txt and return group counts only.
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | HTTPS URL to normalize or cite | |
| host | No | Public hostname | |
| json | No | JSON text to validate; discarded after the check | |
| zone | No | IANA timezone name |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must carry behavioral transparency on its own. It discloses that the tool fetches a public robots.txt and returns counts, but omits error behavior, network expectations, redirects, missing-robots handling, or any side effects.
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, well-structured sentence that front-loads the action and states the output restriction. There is no unnecessary verbiage or repetition.
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?
Given the tool has four parameters and no output schema, the description is incomplete. It does not explain which parameter is actually needed, how the parameters relate to fetching robots.txt, or what the 'group counts' represent, making the tool effectively unusable from the provided context.
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 parameter descriptions are clearly mismatched with the tool's purpose: 'url' says 'normalize or cite', 'json' says 'validate; discarded after the check', and 'zone' says 'IANA timezone name'. These appear copied from other tools and provide no useful meaning for inspecting robots.txt, leaving 'host' ambiguous relative to 'url'.
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 the action ('Fetch'), the target resource ('public robots.txt'), and the exact return shape ('group counts only'). This leaves no ambiguity about the tool's primary purpose.
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?
No guidance is given for when to use this tool versus the sibling tools, such as normalize-url or validate-json. The 'only' qualifier hints at a narrow output, but not at the appropriate use case or conditions.
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.
Most tools have distinct outputs, but citation and normalize-url overlap in URL parsing, and timezone and utc-time both return current time. 'compatibility' is vague and could be confused with citation's request classification.
Names are all lowercase hyphenated, but they mix noun phrases (citation, status-catalog, iana-zones) with verb phrases (normalize-url, inspect-robots, validate-json). 'cc-gb' and 'compatibility' do not follow a clear pattern.
Eleven tools is within a reasonable range and not overwhelming. The set is broad but each tool serves a distinct utility purpose, so the count feels acceptable.
The tools cover common web/network utilities like URL parsing, time zones, HTTP statuses, and JSON validation, but the domain is not clearly defined. Obvious companions such as a direct HTTP fetch or DNS/WHOIS lookup are missing.