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, so the description carries the full burden. It discloses that the tool fetches a public resource, but it does not mention network behavior, error handling, rate limits, caching, or what happens when the robots.txt is unavailable.
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 efficient sentence with no filler. However, it is so terse that it omits parameter relevance and output details, so it is concise but slightly under-specified.
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?
With no output schema and a confusing four-parameter schema, the description should clarify which parameters apply and what 'group counts' means. It does neither, leaving an agent likely to pass unrelated or incomplete arguments.
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?
Although schema description coverage is 100%, the parameter descriptions are mismatched with the tool's stated purpose: 'json' and 'zone' are irrelevant to fetching robots.txt, and the URL/host descriptions are not framed as robots.txt inputs. The description adds no parameter-to-purpose mapping.
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 a specific action ('Fetch a public robots.txt') and the expected output ('return group counts only'). It is distinct enough from the sibling tools, though 'group counts' is not fully defined.
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 normalize-url, domain-shape, or compatibility. No conditions, exclusions, or recommended scenarios are provided.
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 are distinct, but there is overlap in the URL/time clusters: citation, normalize-url, and domain-shape all involve host/scheme data, while timezone and utc-time both return current time. The vague compatibility tool also adds ambiguity.
Names mix noun-only forms (citation, timezone), verb-object forms (inspect-robots, normalize-url, validate-json), and compound nouns (iana-zones, status-catalog, utc-time). There is no consistent naming convention across the set.
Ten tools is a reasonable count for a general-purpose utility server. Each tool is lightweight and the set is neither bloated nor too sparse.
The domain is an open-ended 'utility index,' so completeness is hard to define; it covers URL handling, time, HTTP status, robots, and JSON validation. However, obvious common utilities like hashing, encoding, or string operations are absent, leaving notable gaps for a general utility server.