Short catalog of common HTTP status codes.
| 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, and the description does not disclose side effects, output format, or read-only behavior. The word 'catalog' implies a read-only lookup, but this is not made explicit.
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 only one sentence and has no fluff, which is concise. However, it is too sparse to convey useful structure or operational details, so the brevity works against clarity.
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 tool is underspecified: no return format, no explanation of the parameters' relevance, no example, and no output schema. The description alone is not enough for an agent to know what to pass or what to expect.
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 every parameter has a description, the descriptions are unrelated to HTTP status codes: url is 'HTTPS URL to normalize or cite', json is 'JSON text to validate; discarded after the check', and zone is 'IANA timezone name'. These appear copied from other tools and do not clarify how they relate to this catalog.
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 identifies the tool as a catalog of common HTTP status codes, which matches the name. However, it does not specify the exact action (e.g., 'returns' or 'lists') beyond the noun 'catalog'.
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 about when to use this tool versus the many sibling tools. The description does not mention any use case, prerequisites, or exclusions.
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 have distinct inputs and outputs, but citation and normalize-url both inspect URLs, while timezone, tz-america-chicago, and utc-time all return current time. Descriptions clarify the differences, but compatibility is vague and could be confused with status-catalog or citation.
All names are lowercase and hyphenated, which is readable, but they mix verb-led names like inspect-robots and normalize-url with noun-led names like citation, domain-shape, and status-catalog. There is no consistent verb_noun or action pattern across the set.
Eleven tools is not inherently excessive, but for a server named 'America/Chicago clock' only four tools relate to time. The remaining seven URL, HTTP, robots, and JSON utilities are off-purpose, making the count feel bloated and unfocused.
The time-related tools cover current time in Chicago, UTC, named IANA zones, and a zone list, so the clock core is usable. However, there is no timezone conversion or date arithmetic, and the unrelated utilities do not form a coherent broader domain, leaving the overall surface incomplete.