Return host, scheme, and HTTP status for a URL. Page content is not stored.
| 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 provided, the description carries the full burden of disclosing behavior. It does mention 'Page content is not stored,' which is a useful guarantee. However, it omits other important behaviors such as whether it makes a network request, follows redirects, or handles invalid URLs. The transparency is partial, hence a 3.
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 extremely concise—two short sentences—with no filler or redundancy. It front-loads the primary action and includes one relevant behavioral note. It is optimally sized for a simple tool.
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 the mismatch between the description and the schema parameters, plus the lack of output schema or error behavior, the description is not complete enough for an agent to fully understand the tool's capabilities and constraints. It fails to explain the role of three out of four parameters, making the tool's overall behavior ambiguous.
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 has four parameters (url, host, json, zone), but the description only references URL functionality. The parameter descriptions in the schema are present but unrelated to the tool's stated purpose, and the description does not clarify how host, json, or zone fit into the tool's behavior. This leaves significant semantic gaps for an agent trying to use the tool correctly.
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 tool's purpose: 'Return host, scheme, and HTTP status for a URL.' It uses a specific verb ('Return') and identifies the resource (host, scheme, HTTP status for a URL). This distinguishes it from sibling tools like normalize-url or validate-json.
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 does not provide guidance on when to use this tool versus its siblings. It lacks any explicit comparison or contextual cues, such as 'Use this when you need a quick HTTP status check.' The only additional note, 'Page content is not stored,' offers a minor hint but no actionable selection criteria.
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 have distinct inputs and outputs, but citation and normalize-url both inspect URLs, while timezone, tz-america-chicago, and utc-time all return current time. Descriptions clarify the differences, but compatibility is vague and could be confused with status-catalog or citation.
All names are lowercase and hyphenated, which is readable, but they mix verb-led names like inspect-robots and normalize-url with noun-led names like citation, domain-shape, and status-catalog. There is no consistent verb_noun or action pattern across the set.
Eleven tools is not inherently excessive, but for a server named 'America/Chicago clock' only four tools relate to time. The remaining seven URL, HTTP, robots, and JSON utilities are off-purpose, making the count feel bloated and unfocused.
The time-related tools cover current time in Chicago, UTC, named IANA zones, and a zone list, so the clock core is usable. However, there is no timezone conversion or date arithmetic, and the unrelated utilities do not form a coherent broader domain, leaving the overall surface incomplete.