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 a key behavioral trait—query and fragment are dropped—which tells the agent what not to expect in the result. However, it does not describe error handling or how the unrelated host, json, and zone parameters affect behavior, slightly lowering completeness.
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 two short sentences with no filler. The main action is front-loaded, and the important behavioral note about dropped query/fragment appears immediately after, making the high-value information easy to parse.
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?
While the core URL behavior is stated, the description is incomplete given the tool's actual input schema. It does not explain why host, json, and zone are accepted, what role they play, or how they relate to the stated purpose. There is also no output schema and no annotation to fill in these gaps, leaving an agent with an ambiguous contract for a 4-parameter tool.
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 baseline is 3. The description does not add meaning beyond the schema for url, and it ignores the host, json, and zone parameters entirely. Their schema descriptions are present, but the description adds no context connecting them to URL normalization.
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 uses a specific verb and resource: 'Return origin, host, and path for a URL.' It also clarifies a key scoping behavior—query and fragment are dropped—which makes the tool's function immediately distinct from generic URL utilities or validation siblings.
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?
There is no explicit guidance on when to use this tool versus alternatives. The description does not mention any preconditions, exclusions, or sibling tools such as validate-json or timezone, leaving the agent to infer the use case from the tool name and first sentence.
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: citation and normalize-url both decompose URLs into host/scheme, http-200 is a single-code subset of status-catalog, and timezone/utc-time both give current time. compatibility is too vague to position relative to the others, so an agent could easily select the wrong tool.
All names use lowercase-with-hyphens, but the style mixes nouns (status-catalog, timezone), verbs (normalize-url, validate-json), and code-like labels (http-200). There is no consistent verb_noun pattern, though the naming remains readable.
Eleven tools is within a reasonable range for a web/HTTP utility server. However, a few tools could be consolidated (http-200 into status-catalog, utc-time into timezone), so the count is slightly higher than needed but not excessive.
The set covers common status-code lookup, URL parsing, robots.txt inspection, JSON validation, and time retrieval, but it lacks natural complements such as timezone conversion, header inspection, or URL construction. These gaps are workable, but they make the surface feel incomplete for a general HTTP/URL utility tool.