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?
No annotations are present, and the description does not disclose any behavioral details such as network access, side effects, rate limits, or error handling. The tool's behavior is entirely opaque beyond the vague 'fetch' action.
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 concise and front-loaded with the core action, but it omits essential context and clarification. It is short but not sufficiently informative.
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?
The tool is incomplete for practical use: no output schema is defined, the parameter meanings are unclear, and there is no explanation of what 'group counts' refers to. The description fails to provide a complete picture for an agent to invoke it correctly.
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 schema descriptions are generic and mismatched (e.g., 'HTTPS URL to normalize or cite', 'JSON text to validate; discarded after the check', 'IANA timezone name'). These do not relate to fetching a robots.txt file, providing no meaningful semantic value for the parameters.
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 clear action ('Fetch a public robots.txt') but the parameter names (url, host, json, zone) do not align with that purpose, creating confusion about what the tool actually does. It does not clearly distinguish from sibling tools like timezone or validate-json.
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 provided on when to use this tool versus alternatives. There is no mention of scenarios, prerequisites, or context in which 'inspect-robots' would be appropriate.
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.
Each tool has a distinct purpose (country code, URL manipulation, timezone, JSON validation, etc.) with no overlapping functionality, so there is no ambiguity in selecting the right tool.
All names use lowercase with hyphens, but the pattern is inconsistent: some are noun-only (e.g., 'cc-jp', 'iana-zones') while others are verb-noun (e.g., 'normalize-url', 'validate-json'). The style is uniform but the grammar is mixed.
With 11 tools, the count is reasonable, but the collection feels like a random assortment of utilities rather than a focused feature set, making the size slightly unjustified.
There is no coherent domain to evaluate completeness against. The tools span unrelated areas (ISO, HTTP, timezones, JSON, robots), so the set is incomplete for any single purpose and lacks a clear scope.