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 adds a useful behavioral detail beyond the schema: query and fragment are dropped. However, since there are no annotations, the burden is higher; it does not disclose whether the operation is read-only, whether it performs network calls, or how it behaves for non-URL inputs.
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 concise sentences with zero filler. The primary function is front-loaded and the important caveat about query/fragment appears immediately after.
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 four parameters, but the description only explains the 'url' parameter. 'host', 'json', and 'zone' are completely absent from the description, and there is no output schema or return format beyond 'origin, host, and path'. This is a major gap for a tool with multiple distinct input types.
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 the schema already documents each parameter. The description adds no additional meaning for 'host', 'json', or 'zone', leaving their roles unexplained.
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 verb ('Return'), a clear resource ('URL'), and exactly what is produced ('origin, host, and path') plus what is discarded ('query and fragment'). It unambiguously defines the tool's core purpose and distinguishes it from generic 'normalize' tools.
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 when-to-use guidance is given. The description does not mention any alternative tools, exclusions, or conditions that would help an agent choose this tool over the sibling tools.
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 operate on URLs and return overlapping metadata (citation vs normalize-url vs compatibility), and timezone overlaps with tz-australia-sydney. While descriptions add detail, an agent could easily select the wrong tool for host/status or local-time tasks.
Tool names mix single nouns (citation, timezone), hyphenated noun compounds (domain-shape, status-catalog), and verb_noun commands (inspect-robots, validate-json). There is no consistent verb_noun or resource_action pattern, making the surface feel ad hoc.
Eleven tools is not inherently too many, but for a server named 'Australia/Sydney clock' the majority of tools are unrelated URL/HTTP/JSON utilities. The set would be better split into a clock server and a web-metadata server.
The time-related surface is reasonably complete with UTC, named timezone, Sydney time, and a zone catalog, but notable gaps remain such as timezone conversion and offset information. The URL/HTTP tools cover several metadata operations but lack obvious related operations, so overall domain coverage is uneven.