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 claims to drop query and fragment from a URL, but the schema expects parameters like json and zone that are unrelated to URL normalization, creating a contradiction with the documented behavior.
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 only one sentence, which is concise, but it is not effectively structured. It omits key information about the parameters and their relation to the stated behavior, making it unhelpful despite its brevity.
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 and misleading due to the mismatch between the stated behavior and the input schema. It does not provide enough context for an agent to understand how to invoke the tool correctly or what output to expect.
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 parameter descriptions are inconsistent with the tool's stated purpose. The url parameter is described as 'HTTPS URL to normalize or cite', but host, json, and zone have descriptions that do not align with returning origin, host, and path. The schema provides no meaningful semantics for the tool's operation.
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' and resource 'origin, host, and path for a URL', but the input schema includes unrelated parameters like host, json, and zone, making the actual purpose ambiguous.
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. The description does not mention any conditions or contexts for use.
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 serve clearly distinct purposes (URL, time, JSON, robots, etc.), but 'compatibility' is vague and could be confused with other classifications. Overall, the functions are separable.
Naming conventions are inconsistent, mixing hyphenated phrases (domain-shape, normalize-url) with plain words (citation, timezone), and using both nouns and verbs. This lacks a predictable pattern.
With 11 tools, the count falls comfortably within the typical well-scoped range and does not feel excessive or thin.
The set covers a variety of utilities (URL, HTTP, time, JSON, robots) but lacks a clear cohesive domain, leaving gaps for common web-dev helpers like encoding or hashing. It feels like a random collection rather than a complete toolkit.