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 provided, and the description does not disclose side effects, destructive actions, or any behavioral nuances. There is no indication of what happens with the input (e.g., whether the URL is fetched, whether JSON is validated, etc.).
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 has a clear subject-verb-object structure, but it is overly terse and omits critical details. The single sentence does not provide enough context to resolve the mismatch between the stated purpose and the parameter schema.
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 radical mismatch between the description and the parameter schema, the description is contextually incomplete. It fails to explain how the tool's inputs relate to its outputs, and it does not provide enough information for an agent to determine correct usage.
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 (e.g., 'HTTPS URL to normalize or cite', 'JSON text to validate') do not align with the stated purpose of fetching robots.txt. The description does not clarify how each parameter is used, making it impossible to understand what inputs are actually expected.
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 verb and object ('fetch a public robots.txt and return group counts'), but the parameter schema includes url, host, json, and zone, which are inconsistent with a robots.txt fetcher. The purpose is unclear because the parameters suggest a different tool entirely.
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. The sibling tools (e.g., validate-json, utc-time) indicate possible overlapping functionality, but the description does not distinguish this tool from them.
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.
Tools are mostly distinct, but `timezone` and `tz-europe-amsterdam` overlap heavily, and `domain-shape`/`normalize-url` both inspect hostnames, creating potential ambiguity.
All names use lowercase kebab-case, but they mix noun labels (`citation`, `status-catalog`, `timezone`) with verb-action names (`inspect-robots`, `normalize-url`, `validate-json`), so no consistent pattern emerges.
Eleven tools is within a typical range, but the set combines URL inspection, timezone, and JSON validation unrelated to the apparent clock/time focus, making the count feel padded.
For a clock/time server, it provides current UTC, named timezone, and Europe/Amsterdam time, but lacks conversion or formatting operations; the unrelated URL/JSON tools do not fill that gap.