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?
The description mentions 'fetch' but does not disclose any potential side effects, network behavior, rate limits, caching, or error handling. With no annotations to fill this gap, the agent has no information about the tool's operational characteristics.
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, short sentence that is direct and to the point. There is no unnecessary verbiage, and the main action is front-loaded.
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 four ambiguous parameters and the lack of explanation about the output format or the meaning of 'group counts', the description is far from complete. An agent would not know how to invoke this tool correctly or interpret its results.
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 parameters (url, host, json, zone) are described with generic phrases that clearly belong to other tools (e.g., 'JSON text to validate' for validate-json, 'IANA timezone name' for timezone). The description does not explain how any of these relate to inspecting robots.txt, making the parameters misleading and unusable.
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 action (fetch public robots.txt) and output (return group counts only), which distinguishes it from the sibling tools like normalize-url or validate-json. However, it does not clarify what 'group counts' means or how the parameters fit, so it is not fully self-explanatory.
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?
There is no guidance on when to use this tool versus alternatives, such as when a robots.txt check is needed or when another tool like normalize-url would be more appropriate. The description provides no usage context or prerequisites.
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 serve clearly distinct purposes (URL, time, JSON, robots, etc.), but 'compatibility' is vague and could be confused with other classifications. Overall, the functions are separable.
Naming conventions are inconsistent, mixing hyphenated phrases (domain-shape, normalize-url) with plain words (citation, timezone), and using both nouns and verbs. This lacks a predictable pattern.
With 11 tools, the count falls comfortably within the typical well-scoped range and does not feel excessive or thin.
The set covers a variety of utilities (URL, HTTP, time, JSON, robots) but lacks a clear cohesive domain, leaving gaps for common web-dev helpers like encoding or hashing. It feels like a random collection rather than a complete toolkit.