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 discloses that the tool does not fetch WHOIS or ownership data, which is a behavioral trait. However, it does not specify whether the operation is read-only, can fail, or has other side effects. Given no annotations are provided, the description carries the burden and provides minimal 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 a single sentence, which is concise and front-loaded with the primary action. The extra phrase about WHOIS data is a minor addition but does not bloat the description.
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 because it does not explain how the parameters relate to the action. The mismatch between the description and the schema parameters creates confusion, and the description does not provide sufficient context for an agent to understand what inputs are expected or how they are used.
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 parameters (url, host, json, timezone) are completely mismatched with the described purpose of splitting a hostname into labels. The parameter descriptions appear to be copied from other tools (e.g., normalize-url, validate-json, timezone) and do not relate to the tool's stated function. This is a severe semantic disconnect.
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 verb 'Split' and the resource 'hostname' into labels, which is a specific action. The additional phrase 'without WHOIS or ownership data' clarifies a non-goal, but it does not detract from the core purpose.
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 offers no explicit guidance on when to use this tool versus alternatives. The phrase 'without WHOIS or ownership data' implies that WHOIS-related operations are out of scope, but it does not name specific sibling tools or conditions for 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 heavily: timezone, tz-pacific-auckland, and utc-time all return current time, and URL/HTTP tools like citation, compatibility, normalize-url, and domain-shape have unclear boundaries. Agents would likely struggle to pick the right one.
Names are mostly lowercase hyphenated, but mix verb-object forms (inspect-robots, normalize-url, validate-json) with noun-like labels (citation, compatibility, timezone) and an inconsistent specific alias (tz-pacific-auckland vs timezone).
Eleven tools is not inherently excessive, but for a server named as a Pacific/Auckland clock, at least seven tools are unrelated URL/HTTP utilities and several time tools are redundant, making the set feel padded and poorly scoped.
The time-related subset covers current time, UTC, and IANA zone names, so it is largely complete for a simple clock. However, the mixed URL/HTTP and validation tools have no clear unified domain, leaving the overall surface incomplete and hard to reason about.