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 the full burden of explaining behavior, but it only says 'split a hostname into labels' and what it does not do. It does not mention return format, error behavior, or side effects.
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 short and front-loaded with the main action, but the misleading negative clause and lack of essential parameter information reduce its effectiveness.
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 definition is incomplete for an agent to call it correctly. The parameter names and descriptions conflict with the stated purpose, and no output schema or usage context is provided.
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 schema parameters are clearly mismatched: 'url' is described as an HTTPS URL to normalize, 'json' as JSON text to validate, and 'zone' as an IANA timezone. These descriptions appear copied from other tools and do not relate to splitting a hostname into labels.
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 the tool splits a hostname into labels, which is a specific action with a clear resource. However, it does not clarify how this differs from sibling tools like normalize-url or status-catalog, and the negative phrase 'without WHOIS or ownership data' adds ambiguity.
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 versus alternatives. The description omits any context for choosing domain-shape over normalize-url or other related tools.
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.
Tools are individually distinct in their operations, but the mix of URL, timezone, JSON, and temperature topics creates confusion about which tool applies to a given task. Names like 'compatibility' and 'citation' are vague and could be misinterpreted.
Naming conventions are inconsistent: some tools use hyphenated lower-case (f-to-c, iana-zones), others use single words (citation, timezone), and some use multi-word phrases (normalize-url, validate-json). This lack of a uniform pattern reduces predictability.
At 11 tools, the count is within the typical range, but it feels excessive for a server ostensibly dedicated to Fahrenheit-to-Celsius conversion. The number is inflated by unrelated utilities, making the set poorly scoped for the stated purpose.
For a Fahrenheit-to-Celsius converter, there is only one relevant tool (f-to-c). Essential operations like Celsius-to-Fahrenheit, Kelvin conversions, or batch conversions are missing, so the domain coverage is severely incomplete.