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?
Adds a meaningful behavior with 'No identifiers are retained' and notes that JSON is 'discarded after the check.' With no annotations provided, the description carries the full burden, but it does not mention other side effects, return values, or authentication needs.
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 filler. The core purpose and a key behavioral guarantee are front-loaded.
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 classification tool with 4 optional parameters and no output schema, the description is reasonably complete, but it lacks details about the return format, error cases, or how the classification integrates with citation and validation workflows.
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 parameters are already well documented. The description adds a small privacy note for json but doesn't explain how each parameter relates to the 'classification' action.
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?
States a clear verb and resource: 'Show how this request is classified.' The privacy note ('No identifiers are retained') adds clarity, but the description doesn't explicitly distinguish it from sibling tools like citation 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?
Usage context is implied ('this request', 'normalize or cite', 'discarded after the check'), but there is no explicit guidance on when to use this tool versus its siblings or when not to use 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.
Several tools overlap in the URL/HTTP space, especially citation and normalize-url both returning host/scheme information, with inspect-robots and status-catalog adding to the confusion. The timezone tools are distinct, but compatibility is too vague to place, and the overall set makes tool selection ambiguous.
All names are lowercase and hyphenated, but the semantic pattern is inconsistent: some are verb-object commands like normalize-url and validate-json, while others are bare nouns like citation and timezone, or noun phrases like status-catalog and iana-zones. There is no consistent verb_noun convention or recognizable family pattern.
For a server advertised as 'Hex color to RGB,' 11 tools is far more than needed, and only hex-rgb actually matches that purpose. While 11 is not an extreme number in general, the unrelated utilities make the server feel bloated and mis-scoped.
The set has no coherent domain to assess against, spanning URL parsing, HTTP status, timezones, JSON validation, robots.txt, and color conversion without covering any one area deeply. For the stated hex-to-RGB purpose it is technically complete, but for the apparent mixed utility scope there are clear gaps such as timezone conversion or URL encoding.