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?
With no annotations, the description carries the full burden. It mentions 'group counts only', implying an aggregated result, but does not disclose network-fetch characteristics, error/redirect behavior, or whether the operation is read-only. The safe-read nature is only implicit.
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?
A single tight sentence with no filler. The core purpose and output shape are front-loaded and every word earns its place.
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 definition is too sparse for a tool with four unrelated-looking parameters and no output schema. It does not explain what 'group counts' means, what the return format is, or how the parameters map to the operation, leaving a well-meaning agent to guess.
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?
Schema coverage is 100%, but the parameter descriptions are generic and seem mismatched to fetching robots.txt (e.g., 'normalize or cite', 'JSON text to validate'). The tool description adds no clarification on how url, host, json, and zone relate to the task, so an agent cannot confidently select or fill 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 verb ('fetch') and resource ('public robots.txt') with a specific output ('group counts only'). It is understandable on its own, though it does not distinguish itself from sibling tools by name.
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 given for when to use this tool versus alternatives, and no exclusions or prerequisites are mentioned. The description is purely functional 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.
Citation, normalize-url, and domain-shape all process URLs or hostnames with partially overlapping outputs, while timezone, utc-time, and iana-zones cluster into a separate time-related group. Compatibility is especially vague and adds confusion.
All tool names share a lowercase-hyphen style, but they mix noun phrases like citation and status-catalog with imperative verbs like normalize-url and validate-json. The naming is readable but not consistently patterned.
Ten tools is a reasonable, navigable number for a utility server. However, several tools such as timezone, iana-zones, and validate-json feel tangential to the apparent HTTP Status focus, so the count is slightly over-inclusive.
The tool set mixes HTTP/URL, time, and JSON validation concerns without forming a coherent workflow or domain coverage. Significant gaps remain, such as HTTP header inspection, timezone conversion, and broader URL or JSON operations.