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 provided, so the description carries the burden of behavioral disclosure. It does usefully state that query and fragment are dropped, which is a real behavioral trait. However, it does not disclose behavior for invalid URLs, non-HTTPS inputs, or what happens when the other schema parameters (host, json, zone) are supplied.
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, zero filler, and the most important behavioral constraint ('Query and fragment are dropped') is front-loaded. Every word earns its place.
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?
Given four parameters, no required fields, and no output schema, this short description is not complete enough. It explains the URL path but leaves the host, json, and zone parameters unexplained, and it does not describe the return structure beyond naming three components. An agent would be uncertain how to invoke the tool for most of its declared inputs.
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 each parameter has a baseline description. The tool description adds semantics only for the url parameter (defining the output and dropped components) but says nothing about host, json, or zone, which appear unrelated to the stated behavior. The baseline 3 applies, but the description does not help reconcile the confusing parameter set.
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 names a specific action ('Return') and concrete outputs (origin, host, path) for a URL, with a clear note that query and fragment are dropped. It is clear for the main URL-normalization use case, though it does not explicitly distinguish itself from sibling tools or mention the other parameters in the schema.
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 implies when to use the tool (when you need origin, host, and path without query or fragment) but provides no explicit guidance about alternatives, exclusions, or conditions. With four unrelated-looking parameters and a sibling list, the agent is left to infer appropriate usage.
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 clearly different outputs, but there are overlapping clusters: citation, normalize-url, and domain-shape all deal with URL/hostname shapes, while timezone, utc-time, and iana-zones all cover time. A couple of vague names like compatibility and citation could also cause initial misselection.
All names are lowercase hyphenated, which gives a visual consistency, but they mix verb-led names like normalize-url and validate-json with noun-led names like status-catalog and timezone. The pattern is readable but not predictable enough to be considered strongly consistent.
11 tools is within a reasonable range and none feels redundant, but the collection spans several unrelated concerns such as URL handling, HTTP status, time, JSON validation, and robots.txt. It is slightly broad, though not bloated.
The set covers common lookups like URL normalization, status codes, time, and JSON validation, but there is no coherent domain that ties these together. Obvious adjacent operations such as redirect checking, response header inspection, or rate-limit-specific details are missing, leaving an agent with possible dead ends.