Current time in a named IANA timezone.
| 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?
There are no annotations to indicate read-only or side-effect behavior, and the description does not disclose what the tool returns, whether it performs a lookup, or any other behavioral details. The description fails to carry the burden of transparency in the absence of annotations.
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 terse, but it is not appropriately structured or front-loaded with useful information. It omits critical details about parameters and behavior, so its brevity is a liability rather than a strength.
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 given the schema's complexity and the presence of seemingly irrelevant parameters. There is no output schema, no explanation of the relationship between the parameters and the tool's purpose, and no context about expected inputs or results.
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 lists four parameters (url, host, json, zone) but the description only vaguely references the timezone. The parameters url, host, and json are completely unexplained and appear unrelated to the stated purpose, leaving the agent without any understanding of how to fill them.
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 'Current time in a named IANA timezone' is a noun phrase rather than a clear verb-based action, and it does not distinguish this tool from sibling time-related tools like tz-utc or utc-time. It leaves ambiguity about what exactly is returned or how the timezone is used.
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 versus alternatives such as tz-utc or utc-time. The description does not mention any conditions, prerequisites, or scenarios where this tool is preferred.
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.