Return origin, host, and path for a URL. Query and fragment are dropped.
| 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. It does disclose one behavioral trait ('Query and fragment are dropped') but does not mention how invalid URLs are handled, whether protocol/case are preserved, or what the actual return structure looks like beyond three components. The unrelated schema parameters also muddy the behavioral picture.
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 sentences with no wasted words. The description is front-loaded with the main action and immediately states an important behavioral constraint. This is an efficient structure.
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 4 parameters and no output schema, but the description explains only one parameter's purpose and says nothing about the others. The mismatch between the description and schema is a critical gap. An agent cannot fully understand when or how to use this tool without resolving that inconsistency.
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 baseline is 3. However, the description only addresses the 'url' parameter and does not help reconcile why 'json' and 'zone' belong in a URL-normalization tool. The schema descriptions are clear individually, but the lack of description-level integration leaves parameter roles confusing.
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 specific action and output ('Return origin, host, and path for a URL') and notes a key behavior (dropping query and fragment). This makes the tool's primary purpose clear. However, it does not explicitly distinguish itself from sibling tools, and the input schema introduces unrelated parameters (json, zone) that create ambiguity.
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?
The description gives no guidance on when to use this tool versus alternatives. Given siblings like validate-json and timezone, the presence of 'json' and 'zone' parameters in the schema could mislead an agent, but no exclusion or routing advice is provided.
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 timezone/utc-time both return current time and citation/normalize-url both inspect URL components. Compatibility is vague and could be confused with status-catalog, though descriptions provide some help.
All tool names use lowercase-hyphenated style, but they mix noun labels (citation, timezone, status-catalog) with verb-object actions (inspect-robots, normalize-url, validate-json). This mixed semantic pattern makes naming less predictable despite the consistent formatting.
Eleven tools is not inherently too many, but a server titled 'Leap year check' carries only one leap-year tool among unrelated URL, time, HTTP, and JSON utilities. This is a major scope mismatch for the stated purpose.
The set lacks a coherent domain, so completeness is hard to assess: for a leap-year server there is only the bare check, and as a general utility server there are obvious omissions like date arithmetic or more detailed HTTP capabilities. Agents would hit dead ends beyond the narrow included functions.