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 does disclose that query and fragment are dropped, which is useful behavioral information. However, with no annotations, it omits other important behavior such as error handling, input validation, or whether the operation is read-only.
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, front-loaded sentence that conveys the core behavior without unnecessary words. It is appropriately concise for the stated purpose.
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 fails to address the extraneous parameters in the schema and provides no usage context, output format, or error-behavior notes. Given the confusing schema, the description is far from complete enough for an agent to invoke the tool correctly.
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 schema includes three parameters (host, json, zone) whose descriptions are entirely unrelated to URL normalization, and the tool description does not explain them. Only the url parameter is coherent; the rest appear to be copy-paste errors, leaving the parameter semantics confusing and unusable.
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 the tool's function: return origin, host, and path from a URL while dropping query and fragment. This is specific and distinguishes it from the listed sibling 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?
The description gives no guidance on when to use this tool rather than alternatives such as validate-json or domain-shape. It only states what the tool does, not the conditions or context that make it the appropriate choice.
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 purpose: citation, normalize-url, and domain-shape all analyze URLs/hostnames, while iana-zones, timezone, and utc-time all relate to time. compatibility is vague and could be confused with citation or status-catalog. Only a few tools have truly distinct, non-overlapping functions.
All names use lowercase hyphenation, which is a consistent visual style. However, the pattern is inconsistent: some are imperative verbs (normalize-url, inspect-robots, validate-json) while others are noun phrases (citation, compatibility, timezone, status-catalog). The names are readable but do not follow a predictable verb_noun convention.
Eleven tools is a reasonable count for a utility server and falls within the typical well-scoped range. Some tools feel trivial or overlapping, such as lang-it and the multiple time-related tools, but the total is not excessive.
The tool set has no coherent unifying domain: it mixes URL parsing, HTTP status, time, JSON validation, robots.txt, and a language tag. Obvious operations like URL validation, timezone conversion, or HTTP status details are missing, and the grab-bag nature makes it impossible to assess complete lifecycle coverage.