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?
The description discloses that page content is not stored, which is a useful behavioral detail. However, with no annotations present, the description carries the full burden for transparency and omits other potential side effects like network requests, caching, or error behavior.
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 highly concise, using two short sentences to convey the primary function and an important caveat. It is well-structured and free of unnecessary 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?
The description is incomplete in the broader context of the tool. It does not address the additional schema fields, does not describe the output format, and does not clarify how this tool relates to sibling tools. The missing information prevents full understanding of the tool's capabilities and usage.
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 input schema includes four fields (url, host, json, zone) but the description only mentions the URL. It does not explain the purpose of host, json, or zone, leaving the agent unable to correctly populate or interpret these parameters. The description adds no meaning beyond the schema itself.
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 returns host, scheme, and HTTP status for a URL, which is a specific action. It does not explicitly differentiate itself from sibling tools like normalize-url or status-catalog, but the core purpose is unambiguous.
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 provides no guidance on when to use this tool versus alternatives. It does not mention any conditions, preferences, or exclusions, leaving the agent without direction on tool 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.
Most tools have distinct purposes, though time-related tools (timezone, tz-utc, utc-time) and URL-related tools (citation, normalize-url, domain-shape) share overlapping domains. However, each tool's specific output and intent are clear enough to avoid confusion.
All tools use a consistent lowercase-with-hyphens naming convention (e.g., normalize-url, status-catalog, utc-time). The pattern is uniform and predictable, making it easy to infer function from name.
The server exposes 11 tools, which is a reasonable number for a general-purpose utility. Each tool serves a distinct function without being redundant or excessive, fitting well within the typical range.
The tools cover a broad set of utilities (time, URL parsing, HTTP status, JSON validation, robots.txt), but the server name suggests a clock focus. While time-related functionality is well represented, the additional URL and HTTP tools indicate a mixed-purpose design rather than a fully comprehensive single domain.