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 discloses that query and fragment are dropped, which is helpful behavioral information. However, with no annotations, it does not cover potential errors, return format, or expected behavior for malformed URLs, leaving some behavioral ambiguity.
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 extremely concise and front-loaded. It states the primary output and the key transformation in two short sentences with no filler.
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?
For a simple tool, the description covers its core function, but the presence of extraneous schema parameters and lack of return format or error behavior make the overall context incomplete. The tool description does not fully account for the provided schema.
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 input schema contains four parameters, but the description only explains the 'url' parameter. The descriptions for 'host', 'json', and 'zone' appear irrelevant to a URL normalization tool and are not reconciled in the description, causing significant semantic confusion.
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 returns origin, host, and path for a URL and drops query and fragment. It uses a specific verb and resource, and is distinct from sibling tools like validate-json or inspect-robots, though it does not explicitly name a sibling.
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 given on when to use this tool versus alternatives. It describes what it does but not the conditions under which a user should choose it over other tools such as citation or inspect-robots.
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.
Each tool has a unique, well-defined purpose with no overlapping functionality. For example, 'normalize-url' and 'validate-json' address distinct concerns, and time-related tools are clearly separated.
Tool names follow a mix of conventions: some are verb-object (normalize-url, validate-json, inspect-robots), while others are noun phrases (citation, compatibility, timezone). This inconsistency makes the naming pattern less predictable.
With 11 tools, the count is reasonable and not excessive. Each tool covers a separate utility, though a few could arguably be merged (e.g., timezone and utc-time), but the number is still within a sensible range.
The server name 'Language ja' suggests a language-related domain, yet the tools cover miscellaneous web utilities (URL handling, HTTP status, time, JSON). This mismatch and lack of a cohesive domain make the surface feel incomplete for any specific purpose.