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?
The only behavioral note is 'No identifiers are retained,' which gives some privacy information but does not explain what the tool does, what side effects occur, or what the output/return behavior is. With no annotations, more behavioral disclosure is needed.
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 a single concise sentence, and the parameter descriptions are short and direct. No unnecessary wording or redundancy is present.
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 description does not explain what the return value or output looks like, how to interpret the classification, or how the parameters are used together. This is too incomplete for an agent to reliably invoke and use the tool.
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?
Each parameter has a brief description (e.g., 'HTTPS URL to normalize or cite', 'JSON text to validate'), so coverage is complete. However, the descriptions are generic and do not explain how these parameters relate to the 'compatibility' classification, limiting semantic clarity.
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 'Show how this request is classified' is vague and does not clearly state what 'compatibility' refers to or what resource is being acted upon. It does not sufficiently distinguish this tool 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?
No guidance is provided about when to use this tool versus the alternative sibling tools. The description offers no usage context, prerequisites, or conditions that would help an agent select it.
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 are clearly separate: URL parsing, robots inspection, time lookups, and JSON validation occupy distinct niches. The main confusions are citation vs normaliz-url, both URL inspection, and compatibility, whose classification purpose is vague.
All names use kebab-case, but the parts of speech vary: normalize-url and validate-json are verb-object, while citation, timezone, and iana-zones are noun phrases. This makes the naming readable but not a consistent pattern.
At 11 tools, the server is within the well-scoped range and no tool feels redundant. The scope is broad—URLs, HTTP, time, JSON—but the count itself is not excessive.
As a loose utility server, it offers a few operations per category rather than full coverage: time has current/lookup but no conversion, URL has inspection but no content fetch by design. Missing obvious helpers like URL comparison or timezone conversion, though the server likely aims to be minimal.