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?
No annotations are provided, so the description carries the burden. It accurately communicates a non-destructive, read-only operation and the exclusions, but it does not disclose return format, error behavior, or what happens with malformed input.
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 efficient sentence with no wasted words, and the key functional point is front-loaded. It could slightly benefit from a usage hint, but it is well-structured for its brevity.
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 tool has four optional parameters and no output schema, so the description provides only partial context. An agent can infer the basic operation but lacks information about expected return structure or how invalid input is handled.
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 description coverage is 100%, so the schema already documents each parameter individually. The description adds no additional semantic detail about how the parameters relate to the hostname splitting behavior, keeping this at the baseline.
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 states a specific action ('Split a hostname into labels') and a clear exclusion ('without WHOIS or ownership data'), which clarifies the tool's scope relative to potential lookups. It does not explicitly name sibling tools, so it falls short of a 5.
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?
There is no guidance about when to use this tool instead of alternatives, nor any mention of prerequisites or limitations. The text implies a parsing/filtering utility but leaves the agent to infer appropriate invocation context.
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.
Most tools are distinct, but citation and normalize-url both accept URLs and return host/scheme, so an agent could select the wrong one. timezone/utc-time/iana-zones and compatibility/status-catalog also have overlapping territory, though the descriptions provide some separation.
Names are readable but follow no single convention: some are verb_noun (normalize-url, validate-json, inspect-robots), while others are noun compounds or standalone nouns (timezone, status-catalog, compatibility). This mix is not chaotic, but it lacks a predictable pattern.
11 tools is not excessive, and each utility is small and self-contained. However, the set feels like a grab bag of unrelated utilities rather than a tightly scoped server, and some tools could plausibly be consolidated.
The tools cover basic URL inspection, HTTP status, time lookups, JSON validation, and random generation, but the server's intended domain is unclear. Within that mix, there are notable gaps such as no timezone conversion, no URL encoding/decoding, and no way to inspect HTTP headers, so coverage feels incomplete.