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?
The description clearly discloses the read-only nature (returns parts of a URL) and the specific transformation (drops query and fragment). It does not mention side effects, but none are implied. The absence of annotations means the description carries the full burden, which it fulfills well.
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 and to the point, using a single sentence to convey the core functionality and the dropping behavior. No redundant or unnecessary information 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 is incomplete because it does not address the presence of parameters like 'json', 'host', and 'zone' that have descriptions unrelated to the stated purpose. This mismatch leaves the agent uncertain about the tool's actual interface and behavior.
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 includes parameters (url, host, json, zone) with individual descriptions, but only 'url' aligns with the stated purpose. The descriptions for 'json' and 'zone' are unrelated to URL normalization and are not explained in the tool description, creating confusion about their roles.
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 precisely states the tool's function: returning origin, host, and path for a URL and dropping query and fragment. This is specific and unambiguous.
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 mentions the behavior of dropping query and fragment, which gives some usage guidance. However, it does not explicitly state when to use this tool versus alternatives like domain-shape or inspect-robots, leaving some ambiguity.
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 purpose: `timezone` and `tz-europe-london` both report current time, and `citation`, `normalize-url`, and `domain-shape` all inspect URL components. The mix of URL, HTTP, JSON, and clock tools makes it unclear which tool should be used for a given request.
Tool names mix noun phrases (`citation`, `status-catalog`), hyphenated action verbs (`normalize-url`, `validate-json`), and a specific timezone identifier (`tz-europe-london`). There is no consistent verb-noun or domain-based naming pattern across the set.
The server name suggests a clock/timezone tool, but 11 tools include many unrelated URL, HTTP, and JSON utilities. This is far more than needed for the apparent core purpose, and the extra tools add noise rather than value.
For the clock/timezone aspect, the set provides UTC time, named timezone lookup, and a list of IANA zones, which covers basic needs. However, the inclusion of unrelated URL/HTTP/JSON tools makes the completeness of the overall server muddled, and there is no timezone conversion or formatting utility.