Show how this request is classified. No identifiers are retained.
| 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 were provided, so the description carries full responsibility. The privacy statement 'No identifiers are retained' adds one useful behavioral fact, but the description does not disclose whether the operation is read-only, what side effects occur, or what the classification output looks like.
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?
Two short sentences with no filler; the purpose is stated first and the privacy note is a meaningful addition. Every word earns its place.
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 no output schema and no annotations, the description must explain what the tool returns and how the parameters relate to the classification. It does neither — 'this request' is ambiguous and no return behavior is described. This is inadequate for a tool with four optional inputs and ten siblings.
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?
All four parameters (url, host, json, zone) have schema descriptions at 100% coverage, so the schema already documents them. The description adds no per-parameter meaning, so the baseline of 3 applies.
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 a verb ('Show') and a resource ('this request is classified'), but the classification scheme is never explained, making it hard to understand what the tool actually reports. It does not distinguish it from siblings like validate-json, normalize-url, or domain-shape.
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 given about when to use this tool instead of the ten sibling tools. There is no mention of which inputs are relevant, what problem it solves, or any exclusion criteria.
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 distinct, but several overlap around URLs and time: citation, normalize-url, and domain-shape all operate on URLs/hostnames, while iana-zones, timezone, and utc-time overlap in purpose. The compatibility tool is especially vague and could be confused with citation or status-catalog.
Names are mostly lowercase and hyphenated, but the set mixes noun-style names like citation, timezone, and status-catalog with verb-style names like inspect-robots, normalize-url, and validate-json. There is no consistent verb_noun or noun-only convention, though the names remain readable.
Eleven tools is not an unreasonable count on its own, but the set feels scattershot relative to the server name 'ISO country US,' which implies a focused country-data service. Only one tool actually relates to the country domain, while the rest span unrelated web, URL, time, and JSON utilities.
As a collection of lightweight, privacy-oriented utilities, the surface is reasonably broad. However, the country-data aspect is severely thin with only cc-us, and there are notable gaps like DNS or HTTP header inspection if this is meant to be a general web-utility server.