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 of behavioral disclosure. It does reveal that query and fragment are dropped, which is helpful, but it says nothing about the 'host', 'json', or 'zone' parameters, nor does it describe return formatting or edge cases. The schema suggests additional behaviors that the description omits entirely.
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 sentence with no filler. It front-loads the main output and states the key transformation (query/fragment dropped) 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?
The description is incomplete given the schema's four parameters and no output schema. It covers only URL normalization, leaving the purpose and behavior of 'host', 'json', and 'zone' unexplained. An agent cannot confidently invoke the tool for all its apparent capabilities.
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 coverage is 100%, so each parameter has a description. The tool description adds meaning for the 'url' parameter (dropping query/fragment), but it does not address 'host', 'json', or 'zone'. Baseline 3 applies since the schema already does the heavy lifting.
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 a specific verb and resource: returning origin, host, and path for a URL while dropping query and fragment. This is distinct from raw URL retrieval, but it does not explicitly differentiate itself from sibling tools like 'url' or 'host', and it ignores the other schema fields, which creates some scope ambiguity.
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 provides no guidance on when to use this tool versus sibling alternatives such as 'url', 'host', or 'path'. It only states what it does; there is no mention of conditions, exclusions, or alternative selection.
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 in the URL/host space (citation, normalize-url, domain-shape, inspect-robots), so an agent may need to read descriptions carefully to select the right one. The time and HTTP tools are mostly distinct, but 'compatibility' is vague enough to create selection uncertainty.
All names use lowercase kebab-case, but the underlying convention is mixed: verb-first names like normalize-url and validate-json coexist with noun-first compounds like semver-parse and domain-shape, plus bare nouns like citation and timezone. The set is readable but lacks a consistent naming pattern.
For the broad set of read-only utilities exposed, 11 tools is a reasonable count and none feels redundant. However, the scope spans URLs, time, HTTP status, JSON, and semver, which feels slightly broad for a server whose name implies a narrow 'SemVer numbers only' purpose.
The tools cover several useful read-only operations, including URL inspection, time lookups, status codes, JSON validation, and semver parsing. The overall domain is diffuse, and there are notable gaps such as timezone conversion, URL redirect/validation details, and semver comparison.