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?
With no annotations, the description carries full responsibility for behavioral disclosure. It only states what the catalog contains, not what the tool does when invoked. There is no mention of output shape, lookup behavior, side effects, or how the provided parameters affect execution.
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 short, but it is under-specified rather than appropriately concise. It repeats the tool name instead of earning its place with actionable information. There is no structure or front-loading of key behavioral details.
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 has no output schema and no annotations, but the description does not explain what result to expect or how the four unrelated parameters are used. An agent cannot tell whether this is a read-only lookup, a static list, or something requiring the provided inputs, making the definition wholly inadequate for reliable invocation.
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 description coverage is 100%, and each parameter already has a self-contained description (url, host, json, zone), so the schema carries the parameter documentation. However, the description adds no bridge between these parameters and the stated catalog of HTTP status codes, leaving their role unexplained.
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 is a noun phrase, 'Short catalog of common HTTP status codes,' which largely restates the tool name 'status-catalog' and lacks an action verb. It does not specify whether the tool returns a list of all codes, looks up a specific code, or does something else. It offers only the vague qualifiers 'short' and 'common.'
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 gives no indication of when to use this tool versus any sibling. Worse, the input schema exposes unrelated parameters (url, host, json, zone) with no explanation of how they connect to HTTP status codes, which is misleading for an agent trying to select the right tool.
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.
Timezone, UTC, and Asia/Shanghai tools overlap: timezone can replicate the other two by passing a zone name, and citation/normalize-url both return host/scheme information. The compatibility tool is also vague about what it classifies, adding more boundary ambiguity.
Names are all lowercase and hyphenated, but they mix bare nouns like citation and timezone with verb-object names like inspect-robots, normalize-url, and validate-json. The hardcoded tz-asia-shanghai also breaks the otherwise readable pattern.
Eleven tools is not extreme as a raw count, but for a server named Asia/Shanghai clock only four tools are time-related. The remaining URL, HTTP, and JSON helpers make the surface feel bloated and misaligned with the stated purpose.
The time domain covers basic zone lookups, UTC, and Asia/Shanghai, but lacks offset/DST details or conversion. The unrelated web/json tools create a second half-baked domain with no clear coverage, so the overall set does not feel complete for any single purpose.