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 are provided, and the description does carry some behavioral burden. 'No identifiers are retained' is a meaningful statement about data handling, and the json parameter already notes it is discarded after the check. However, the description does not disclose whether the tool makes network requests, whether it is read-only, what side effects occur, or what the response contains.
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 two short sentences with no filler. The core action comes first and the privacy note is a useful addition. Every sentence 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?
For a tool with four optional parameters, no output schema, and no annotations, the description is incomplete. It does not state what the classification result looks like, what 'compatibility' means, whether inputs are validated individually or together, or what the agent should do with the returned classification. The privacy note is helpful but does not make the tool actionable.
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 coverage is 100%, so all four parameters already have descriptions. The tool description does not add param-specific meaning beyond the schema; 'No identifiers are retained' applies broadly but does not clarify how url, host, json, or zone are used in the classification. Baseline 3 is appropriate.
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 the tool shows how a request is classified, which is a verb plus a result, but it never explains what 'classified' means, what classifications exist, or what output to expect. It is vague rather than a tautology, so it is not a 1 or 2, but it does not clearly distinguish itself from siblings like 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?
There is no guidance on when to use this tool instead of the many sibling validators and formatters. The privacy note 'No identifiers are retained' implies a possible use case, but the description does not say 'use this when you need a privacy-preserving classification' or mention any 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 have distinct outputs, but the URL-related tools (citation, normalize-url, domain-shape) and time-related tools (utc-time, timezone, iana-zones) form overlapping clusters that an agent could misselect. Descriptions clarify the differences, but the boundaries are not immediately obvious.
All names use lowercase hyphenation, but the set mixes imperative verb_noun names (inspect-robots, normalize-url, validate-json) with noun/adjective names (citation, compatibility, timezone, base64-ok). This is readable but not a consistent naming pattern.
Eleven tools is a reasonable size for a general-purpose utility server and none seem redundant enough to cut. A few could be consolidated, such as timezone and utc-time, but the count is not excessive.
The server covers several utility categories, including URL analysis, time, JSON validation, HTTP status, and base64, but has noticeable gaps such as no base64 decode, no timezone conversion, and no URL encoding/decoding. These missing operations limit what an agent can accomplish without another server.