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?
With no annotations, the description carries the burden. It discloses the core behavior (a read-only 'current time' lookup), but it does not state the return format, whether the time is a snapshot at call time, or what happens with an invalid timezone name.
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?
A single, front-loaded sentence with zero wasted words. Every word earns its place.
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?
Fits small scope the description is adequate for selecting the tool, but with no output schema and no annotations it omits the expected return shape and leaves the unrelated url, host, and json parameters unexplained in context. An agent could call it but not know what result to expect.
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 description coverage is 100%, so the schema already documents all four parameters. The description's 'IANA timezone' phrase matches the zone parameter but adds no semantic detail beyond the schema.
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 verb and resource: returns the current time for a named IANA timezone. It is easily distinguished from sibling tools like validate, normalize, or status, though it does not explicitly name the siblings it is not.
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 implies a simple lookup use case but gives no guidance on when to prefer this tool over alternatives, no prerequisites, and no exclusions. An agent must infer that 'zone' is the relevant parameter.
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.
The timezone tools overlap heavily: `timezone` already supports named IANA zones, making `utc-time` and `tz-america-new-york` largely redundant. The URL tools also blur together (`citation` vs `normalize-url` both return host/scheme information), and `compatibility` is too vague to confidently distinguish from the other request-classification tools.
All names share a lowercase hyphenated style, but they mix conventions: verb-prefixed tools like `inspect-robots`, `normalize-url`, and `validate-json` sit alongside noun phrases like `domain-shape`, `status-catalog`, and `utc-time`, plus single-word names like `timezone` and `citation`. The names are readable and predictable in format, but not in action pattern.
Eleven tools is not an extreme number, but the set is not well-scoped: it mixes time, URL normalization, HTTP status, robots.txt, and JSON validation concerns. The count feels like several small toolkits merged into one server rather than a focused tool collection where each tool clearly earns its place.
There is no coherent domain to call complete. As a clock server, it lacks timezone conversion, offsets, or date formatting; as a web utility server, it lacks common operations like fetching content or inspecting headers. Significant operations for either inferred purpose are missing, so agents would likely hit dead ends.