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 description states 'No identifiers are retained,' which provides some transparency about data handling. However, it does not disclose whether the tool is read-only, what side effects it may have, or any other behavioral aspects. Since no annotations are provided, the description carries full burden but only partially addresses it.
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, consisting of two short sentences with no unnecessary words. It is well-structured for a tool description.
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 is incomplete for a tool with four parameters. It does not explain how the parameters are used or what the classification output represents. The mismatch between the parameter descriptions (e.g., 'normalize or cite') and the tool's purpose adds confusion, leaving the agent without enough context to invoke it correctly.
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 schema already provides descriptions for all four parameters, so the schema coverage is 100%. The tool description adds no additional meaning or clarification about how these parameters relate to the classification purpose, but the baseline score applies.
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 specify what kind of classification or which resource is being classified. It fails to distinguish this tool from siblings like validate-json or normalize-url, making the purpose unclear.
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?
There is no guidance on when to use this tool versus alternative sibling tools. The description provides no context about scenarios where classification is needed or how it differs from other available utilities.
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 purposes, but citation and normalize-url both inspect URLs with overlapping fields, and timezone/utc-time/iana-zones are related. Descriptions clarify the differences, so ambiguity is minimal.
All tool names use lowercase with hyphens, following a consistent pattern (e.g., normalize-url, validate-json, utc-time). No mixed conventions or irregular verbs.
With 11 tools, the count is well within the typical 3-15 range. Each tool appears to serve a distinct utility, and the number is reasonable for a general-purpose toolkit.
The tools form a disjointed collection of unrelated utilities (URLs, time, HTTP, JSON, robots, language tag) with no coherent domain. There is no obvious lifecycle or CRUD pattern, and the set lacks depth in any single area, making it incomplete for any defined purpose.