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 discloses that it fetches a public resource and returns group counts, but it omits important behavioral details such as error handling, network assumptions, or whether it follows redirects. With no annotations, the behavior is only minimally transparent.
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, compact sentence that front-loads the core action and output. It contains no filler or redundant wording, so it is highly concise.
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 description does not explain how the four parameters relate to fetching a robots.txt file. The presence of unrelated parameter descriptions makes the tool contextually incomplete and likely to confuse an agent trying 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 parameter descriptions appear copied from unrelated tools: 'url' is described as a URL to normalize or cite, 'json' as JSON text to validate, and 'zone' as a timezone name. These directly conflict with the stated robots.txt purpose and provide actively misleading information about how the parameters should be used.
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 tool fetches a public robots.txt and returns group counts, which is a specific verb and resource. It does not explicitly distinguish itself from sibling tools, but none of the siblings obviously target robots.txt, so the purpose is reasonably clear.
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. It does not mention any preconditions, limitations, or contrasting use cases, leaving the agent to infer when this tool is 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.
Most tools target distinct operations—text counting, JSON validation, robots inspection, time utilities—and descriptions clarify the differences. The main risk is citation versus normalize-url, since both describe URL components, and timezone versus utc-time could occasionally cause misselection.
Names are readable and consistently lowercase, but they mix styles: verb-object names like normalize-url and validate-json, noun compounds like char-count and status-catalog, and single nouns like citation and compatibility. There is no uniform verb_noun pattern.
At 11 tools, the set is well within the ideal range and each utility addresses a separate use case. No obvious redundant or filler tools are present.
The surface covers text validation, URL inspection, robots, time, and HTTP status reasonably well for a privacy-focused utility server. Missing conveniences like timezone conversion or URL encoding are minor and can be worked around.