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 provided, the description carries the behavioral disclosure burden. It adds a meaningful privacy note ('No identifiers are retained'), but it does not explain whether the tool performs remote lookups, mutates anything, or what side effects might occur.
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 concise: two short sentences with no filler. The privacy caveat earns its place, but the brevity leaves operational details missing, so it does not reach the highest tier.
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?
Given four optional parameters, no output schema, no annotations, and a set of sibling tools, this description is too thin. An agent cannot tell what input to provide, how classification output looks, or when this tool should be preferred.
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 input schema already documents all four parameters at 100% coverage. The description adds no extra meaning about how url, host, json, or zone affect classification or whether they are mutually exclusive.
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 an object ('how this request is classified'), so it is not a tautology. However, 'classified' is never defined, and the description does not differentiate this tool from siblings like domain-shape or status-catalog.
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 compatibility versus the sibling tools. The description does not mention whether url, host, json, and zone are alternative inputs or which context calls 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.
Several tools overlap in input or output: citation and normalize-url both inspect URLs, and timezone and utc-time both return current time. The descriptions clarify the intended focus somewhat, but an agent could still misselect between these pairs.
Tool names mix standalone nouns like citation and timezone with verb-noun compounds like inspect-robots and normalize-url, and hyphenation is inconsistent. Most names are still readable and weakly predictable, but there is no strong naming convention.
Ten tools is a moderate count, but the server's apparent 'Robots Inspect' focus is supported by only inspect-robots. The rest are broad URL, time, and JSON utilities, which makes the set feel padded rather than tightly scoped.
For a server named Robots Inspect, robots.txt coverage stops at group counts and offers no way to retrieve actual rules, test URLs against directives, or compare agent policies. The unrelated utilities do not fill this gap, so core inspection workflows would dead-end.