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?
With no annotations, the description carries the full burden of disclosing behavior. It only states that identifiers are not retained; it does not mention whether the operation is read-only, whether it makes network calls, or whether any rate limits or side effects exist. 'Show' weakly implies non-mutating behavior but is not explicit.
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 only two sentences and does not waste words, but the first sentence is vague and the second is the only concrete piece of information. It is concise but under-specified, lacking essential details about the tool's operation.
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?
There is no output schema, no annotations, and four optional parameters, yet the description does not explain what the tool returns, how the parameters are used together, or what classification categories exist. An agent has insufficient context to invoke this tool 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?
The schema covers all four parameters with individual descriptions, so the schema_description_coverage is 100%. The tool description adds no parameter-level meaning and does not explain how url, host, json, and zone relate to the classification, keeping this at the baseline.
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 says 'Show how this request is classified' but never defines what classification means, what resource is being examined, or what kind of result is produced. It does not clearly distinguish this tool from siblings such as validate-json or normalize-url.
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 choose compatibility over the many sibling tools. There are no conditions, prerequisites, or exclusions mentioned, so an agent cannot determine the appropriate context for this 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.
Most tools have distinct purposes, but 'citation' and 'normalize-url' overlap in parsing URLs and returning host/scheme details, while 'compatibility' is vaguely described. Overall, the boundaries are mostly clear.
Names are consistently lowercase and hyphenated, but mix noun-style names ('timezone', 'citation') with verb-style names ('inspect', 'normalize', 'validate'). There is no uniform verb_noun pattern, making the naming style inconsistent.
With 11 tools, the count is reasonable for a utility-focused server and within the typical 3-15 range. Each tool addresses a distinct aspect, though some could be consolidated.
The set covers URL parsing, HTTP status, timezones, robots.txt, language tags, and JSON validation, but lacks broader web-development utilities like DNS lookups or header inspection. The domain is not fully defined, so some gaps are possible.