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 full burden for behavioral disclosure, but it only says what the tool returns. It does not explicitly state that the operation is read-only, how invalid timezone names are handled, or what the output format looks like.
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 a single, front-loaded sentence with no filler or repetition. Every word contributes to the stated purpose, making it an excellent example of conciseness.
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 absence of annotations and output schema, plus a four-parameter schema containing several unrelated fields, the description is too thin to support confident invocation. It should at least state that only zone is used and indicate what the response contains.
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?
Even though the schema has 100% description coverage, three of the four parameters (url, host, json) are unrelated to the stated purpose of returning the current time in a timezone. The description does not clarify that only zone is relevant, and it does not warn that zone is effectively required despite being formally optional.
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 clear verb and resource: it returns the current time for a named IANA timezone. It is specific enough to understand the core purpose, but it does not differentiate from sibling tools such as citation, normalize, or validate.
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 gives no guidance about when to choose this tool over alternatives. The only hint is the implied use case of wanting the current time in a named timezone; no alternatives, exclusions, or conditions are mentioned.
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 target distinct concerns: timezone lookups, URL normalization, JSON validation, and robots.txt inspection are clearly separate. The only real overlap is citation vs. normalize-url, both of which extract host/scheme info from a URL, and iana-zones vs. timezone vs. utc-time could be slightly confusing in a timezone context.
All names use lowercase hyphenated style, which is readable, but they mix noun phrases (citation, compatibility, timezone) with verb-led phrases (inspect-robots, normalize-url, validate-json). There is no consistent verb_noun pattern across the set.
Ten tools is a reasonable count, but the set is not well-scoped to the server's stated IANA Zones identity. Only three tools clearly relate to timezones, while the rest cover unrelated URL, HTTP, and JSON utilities, making the count feel padded rather than purpose-built.
For a timezone-focused server, the surface is incomplete: it offers common names, current time, and UTC, but no comprehensive zone list, offset information, or timezone conversion. The URL and JSON helpers are similarly one-off utilities with no broader workflow coverage, leaving notable gaps in the apparent domain.