Split a hostname into labels without WHOIS or ownership data.
| 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 includes a negative claim ('without WHOIS or data') which hints at what the tool does not do, but it is vague and does not disclose side effects, permissions, or data handling. No annotations are present to supplement transparency.
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 very short but the wording is unclear and potentially misleading. The phrase 'without WHOIS or data' adds confusion rather than clarity, making it inefficient for an agent 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?
The description is incomplete for the tool's complexity. It does not describe expected inputs, outputs, or relationships to the parameter set, and the mismatch between the stated purpose and the given parameters leaves the agent without sufficient context to invoke it 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 description does not explain any of the parameters (url, host, json, timezone). Although the schema provides descriptions, they are generic and mismatched (e.g., 'json' as 'JSON text to validate'), and the tool description adds no clarification or connection to the actual purpose.
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 primary action ('Split a hostname into labels'), which is specific and distinguishes it from sibling tools like normalize-url or validate-json. However, the phrase 'without WHOIS or data' is ambiguous and may confuse about the tool's exact scope.
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. There is no mention of appropriate contexts, limitations, or comparisons to sibling tools, leaving the agent without direction.
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.