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?
There are no annotations provided, and the description does not disclose any behavioral traits such as side effects, permission requirements, rate limits, or whether it performs a read-only operation. The agent is left to infer that fetching a public file is safe and non-destructive.
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 extraordinarily concise, consisting of a single sentence that directly states the action and expected output. It does not waste words and is well-structured.
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 minimal description and the grossly mismatched parameter definitions, the tool is under-specified. The agent has no idea how to set the parameters or what 'group counts' refers to, making the description insufficient for correct usage in 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 in the schema are completely mismatched with the tool's purpose. For example, 'json' is described as 'JSON text to validate; discarded after the check' and 'zone' as 'IANA timezone name', which are irrelevant to fetching robots.txt. The description fails to provide any meaningful semantics for the parameters, leaving the agent confused about how to invoke the tool.
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 nature of the output (group counts only). It is concise and unambiguous enough to understand the primary purpose, though the exact meaning of 'group counts' is slightly vague.
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?
The description provides no guidance on when to use this tool versus alternatives, nor does it mention any prerequisites, conditions, or scenarios where this tool is preferred. It is a single declarative sentence with no usage context.
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 clearly distinct purpose, covering URL analysis, time/date, HTTP status, robots.txt, and JSON validation with no significant overlap or ambiguity.
All tool names use a consistent lowercase-with-hyphens convention, matching the style across the entire set with no mixed casing or underscores.
The set of 11 tools is reasonable for a general-purpose utility server, providing a moderate breadth without feeling bloated or sparse.
The domain appears to be 'web developer utilities,' and while it covers common needs like URL handling, time, HTTP status, and JSON, some expected utilities (e.g., base64, HTML escaping) are missing, making it slightly incomplete.