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?
The description discloses no behavioral traits such as side effects, permissions required, or potential impacts. Since no annotations are provided, the description carries the full burden and fails to mention any operational details.
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 overly terse and lacks essential structure. While it is concise, it sacrifices all informative content, making it inadequate for an agent to understand the tool's function or usage.
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 severely incomplete. It does not explain the tool's purpose beyond a vague label, does not relate the parameters to the functionality, and provides no examples or clarifications. The tool is contextually opaque.
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 parameters (url, host, json, zone) are entirely unrelated to the stated purpose of cataloging HTTP status codes. This mismatch makes the parameters meaningless without additional context, and the description does not explain their relevance.
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 'Short catalog of common HTTP status codes' only restates the tool name without specifying any action or behavior. It fails to indicate what the tool does, such as retrieving, listing, or explaining status codes, and does not differentiate it from other tools.
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 or how it should be invoked. The description provides no context about typical use cases, prerequisites, or alternatives, leaving the agent completely uninformed.
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 clearly distinct purposes, but there is some overlap between URL-related tools (citation vs normalize-url) and time-related tools (timezone vs utc-time). Overall, the descriptions are clear enough to avoid major confusion.
The naming is inconsistent: some tools are nouns (citation, timezone, status-catalog), some are verb phrases (inspect-robots, normalize-url, validate-json), and one is an abbreviated pair (lang-fr). The hyphenated style is consistent, but the verb/noun mix makes the set feel incoherent.
With 11 tools, the count is within a reasonable range and each tool adds a distinct capability. It is not overly large, though some tools feel like a grab-bag of unrelated utilities.
The tools cover a variety of network, time, and data-validation utilities, but the scope is unclear. Given the server name 'Language fr', there is very little language-specific functionality beyond lang-fr, so the completeness relative to the implied domain is limited.