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?
No annotations are present, so the description carries full responsibility. It mentions dropping query and fragment, but does not explain behavior for invalid URLs, empty inputs, or whether the host is extracted from the URL or supplied separately.
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, clear sentence with no unnecessary words. It communicates the main behavior efficiently.
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?
There is no output schema, no example, and no error handling information. The mismatched parameter descriptions further reduce the completeness of the tool contract.
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 'host', 'json', and 'zone' with descriptions that are unrelated to normalizing a URL. The 'url' description is partially relevant, but the other parameters appear mismatched and would confuse an agent trying to call this tool.
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 clearly states that the tool returns origin, host, and path for a URL and drops query and fragment. It does not explicitly distinguish from sibling tools, but the verb and resource are clear enough.
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 on when to use this tool versus alternatives such as validate-json or timezone-related tools. There is no context about typical use cases or prerequisites.
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.
Tools like 'timezone' and 'tz-asia-singapore' overlap in purpose, though the latter is location-specific. Similarly, 'normalize-url' and 'inspect-robots' both relate to URLs but serve different functions. Overall, most tools are distinguishable but a few could cause selection ambiguity.
Names are highly inconsistent: some are verb phrases (e.g., 'normalize-url', 'validate-json'), some are nouns (e.g., 'status-catalog', 'iana-zones'), and there's no unified pattern. Hyphenation is used but not systematically, and the mix of imperative and descriptive naming makes the set feel arbitrary.
With 11 tools, the count is within a reasonable range for a multi-purpose utility server. However, the set feels padded with niche tools like 'tz-asia-singapore' while lacking broader coverage, making the count slightly high for the apparent scope.
The tools cover disparate domains (URLs, timezones, JSON, HTTP status) without forming a coherent service. For a clock/timezone server, there are redundant tools but no common operations like list all timezones or convert between zones. For a URL utility, missing fetch or parse variants. The domain is unclear, leading to significant gaps.