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?
With no annotations, the description carries full burden; it does clarify that no WHOIS/ownership lookup is performed, which is a useful behavioral boundary. However, it does not disclose return format, error behavior, or side effects beyond the split operation.
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 with no unnecessary words. It is concise, though it sacrifices necessary contextual detail.
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?
Given 0 required parameters, 4 optional parameters of different types, no output schema, and no annotations, a one-sentence description is insufficient. The agent cannot determine expected output or which parameters are relevant, especially since url, json, and zone seem unrelated to splitting a hostname.
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 coverage is 100%, so baseline is 3, but the description adds no parameter-level guidance. It does not connect 'hostname' to the host parameter or explain why url, json, and zone are present.
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 explicitly excludes WHOIS/ownership enrichment, making the core purpose clear. However, it does not differentiate from sibling tools, and the input schema's extra parameters (url, json, zone) introduce ambiguity about the intended input.
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 on when to use this tool, what inputs to supply, or how it compares to alternatives. The description only states the operation, leaving the agent to infer usage.
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 URL-focused tools (citation, normalize-url, domain-shape) overlap in what they inspect, though their descriptions do specify different outputs. compatibility and sha256-ok are vague, but most other tools have clearly separate jobs.
All names use lowercase hyphenation, but they mix verb-object names (normalize-url, inspect-robots, validate-json) with noun-only or noun-noun names (citation, timezone, status-catalog, iana-zones). This is readable but gives agents no reliable pattern for predicting tool names.
Eleven tools is within a reasonable size for a general-purpose privacy-safe utility server, and no tool is an exact duplicate. The set could be tightened around a single domain, but the count itself is not excessive.
The server's domain is too broad and unfocused to define a complete workflow: URL inspection lacks redirect/header coverage, timezone handling lacks conversions, and JSON/hash tools are single-purpose checks. As a result, agents will likely need tools outside this server for related operations.