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?
No annotations are provided, so the description carries the full burden of disclosing side effects or read-only behavior. The description only says 'Short catalog' and gives no indication of whether the tool performs lookups, checks, modifications, or has any external effects.
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 extremely short, which is concise, but it omits essential details about the tool's function and parameters. It is front-loaded with the subject matter, but the brevity sacrifices clarity and usefulness.
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 is too minimal to be contextually complete. It does not explain what the catalog contains, how to query it, what output to expect, or how the four seemingly unrelated parameters are used. Given the absence of an output schema, the description leaves the tool's behavior almost entirely unspecified.
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 input schema provides descriptions for all four parameters (url, host, json, zone), so schema coverage is 100%. However, the tool description adds no information about how these parameters relate to the catalog of HTTP status codes, leaving their purpose ambiguous.
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 the tool is a 'Short catalog of common HTTP status codes,' which identifies the subject matter but lacks an action-oriented verb or explanation of what the tool actually does with that catalog. It does not distinguish how this tool should be used relative to its name or purpose.
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, what scenarios it is appropriate for, or how it relates to sibling tools such as validate-json or timezone. The description provides no context for selecting this tool over alternatives.
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 clearly distinct, but 'citation' and 'compatibility' have vague descriptions that could overlap with HTTP status handling, and 'status-catalog' adds further potential confusion. URL-related tools are distinguishable but require careful reading.
All names consistently use lowercase hyphenated style, but they mix noun phrases like 'timezone' and 'status-catalog' with verb-object forms like 'normalize-url' and 'validate-json'. This is mostly predictable but not perfectly uniform.
With 11 tools, the set is reasonably sized and not overwhelming. Each tool appears to serve a single utility purpose, fitting the apparent web-utility domain.
The collection covers common web development utilities: URL handling, HTTP status, time, timezone, JSON validation, robots.txt inspection, and language tags. There are no major dead ends, though the server name 'Language zh' does not strongly align with the broader tool set.