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 behavioral disclosure. It does disclose one meaningful behavior: 'No identifiers are retained.' However, it does not state whether the operation is read-only, what side effects occur, or what 'classified' entails beyond showing a result.
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, front-loaded sentences with no padding. Every sentence serves a purpose: one states the main action, the other addresses a key privacy concern.
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?
The tool has no output schema and no annotations, so the description must explain what 'classification' produces and how the four optional parameters influence it. It does none of that, leaving an agent unable to predict the output or pick sensible arguments.
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 schema already documents url, host, json, and zone. The description adds no parameter-specific meaning; it does not explain how any of the four parameters relate to classification or compatability.
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 gives a verb and an object ('Show how this request is classified'), but the meaning of 'classified' and the relation to the tool name 'compatibility' are left undefined. It is not a tautology, but it is vague and does not distinguish the tool from siblings like normalize-url or validate-json.
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 versus the sibling tools. There are no conditions, exclusions, or mentions of alternatives, so an agent must guess from the name 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.
Most tools have distinct outputs, but there are overlapping clusters: citation and normalize-url both return host information, timezone/utc-time/iana-zones all revolve around time, and domain-shape/punycode-ok both target hostnames. An agent would need to read descriptions carefully to avoid picking the wrong one.
Naming style is inconsistent: some names are verbs (normalize-url, validate-json, inspect-robots), some are nouns (citation, compatibility, timezone), and some are quirky compounds (punycode-ok, iana-zones). The consistent lowercase/hyphen formatting is the only pattern.
Eleven tools is not an unreasonable count by itself, but the server is named for punycode host checking while many tools are unrelated URL, time, and JSON utilities. The set feels padded rather than deliberately scoped.
The tool surface has no coherent domain to be complete against: a punycode host checker would need at least IDN conversion or comparison, while the URL/time/JSON utilities appear as unrelated extras. Significant coverage gaps would likely force agents to combine or externalize work.