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. It adds one useful behavioral guarantee ('No identifiers are retained') but does not disclose whether the tool performs side effects, requires network access, or what happens to supplied data beyond retention.
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 redundancy. The privacy guarantee is concise and arguably the most decision-relevant fact; 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, this description is under-specified. It does not explain what result the agent should expect, how the parameters select the classification mode, or why this tool exists alongside citation, normalize, and validate-json.
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 even though the description adds no parameter-specific meaning. The description doesn't explain how url, host, json, and zone relate to 'classification,' but the schema adequately documents each field's type and intent.
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 names a verb ('Show') and a resource ('this request'), but leaves the key concept—what 'classified' means for a compatibility tool—unspecified. It does not distinguish the tool from siblings like validate-json or normalize beyond the word 'classified'.
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 provided on when to use this tool versus the siblings. The description does not mention prerequisites, typical call patterns, or exclusions, so an agent must guess from the parameter names alone.
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 URL-focused tools (citation, normalize-url, domain-shape) overlap in what they inspect, though their descriptions do specify different outputs. compatibility and sha256-ok are vague, but most other tools have clearly separate jobs.
All names use lowercase hyphenation, but they mix verb-object names (normalize-url, inspect-robots, validate-json) with noun-only or noun-noun names (citation, timezone, status-catalog, iana-zones). This is readable but gives agents no reliable pattern for predicting tool names.
Eleven tools is within a reasonable size for a general-purpose privacy-safe utility server, and no tool is an exact duplicate. The set could be tightened around a single domain, but the count itself is not excessive.
The server's domain is too broad and unfocused to define a complete workflow: URL inspection lacks redirect/header coverage, timezone handling lacks conversions, and JSON/hash tools are single-purpose checks. As a result, agents will likely need tools outside this server for related operations.