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 behavioral disclosure. It says nothing about side effects, output format, parameter handling, or whether this is a read-only lookup. The noun phrase 'catalog' implies a static list, but that is inference, not disclosure.
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 a single short sentence, but it is under-specified rather than appropriately concise. Seven words cannot cover the tool's purpose, parameters, and output expectations.
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?
With four optional parameters, no annotations, and no output schema, this description is severely inadequate. It does not state what action the tool performs, how parameters affect the catalog, what it returns, or when to use it. An agent has almost no chance of invoking it correctly.
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%, so the baseline is 3. The description adds no meaning beyond the schema and fails to explain how the four unrelated parameters (url, host, json, zone) relate to an HTTP status code catalog, but the schema itself at least documents each parameter.
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' is essentially a restatement of the tool name 'status-catalog'. It adds only the qualifiers 'short' and 'common HTTP' but lacks a verb or action, so an agent cannot tell what invoking the tool actually does or how it differs from sibling 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 about when to use this tool versus alternatives. The description never mentions use cases, filters, or related sibling tools, leaving an agent without any context for selection.
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.
Several tools operate on URLs (citation, compatibility, normalize-url, domain-shape, inspect-robots) and several on time (business-day, iana-zones, timezone, utc-time), creating some overlap in input types. The descriptions mostly clarify intent, but citation and compatibility in particular could still be confused.
Tool names mix nouns (citation, compatibility, timezone), verb phrases (inspect-robots, normalize-url, validate-json), and compound labels (business-day, iana-zones, utc-time). There is no consistent verb_noun or other naming pattern across the set.
Eleven tools is not excessive numerically, but the server name 'Weekday vs weekend' suggests a single narrow utility, while most tools are unrelated to that purpose. The set feels scattershot rather than deliberately scoped.
The tools span URL inspection, time/date, and JSON validation without a unifying domain, so there is no coherent capability surface to complete. Each mini-cluster has gaps, such as URL tools that only inspect and time tools that lack conversions or date arithmetic.