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?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the output concept ('Current time') and does not mention time format, DST handling, whether the time is server-side, error behavior, or what happens with an invalid zone 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 sentence with no filler; the essential purpose is front-loaded. It is efficient, though arguably under-specified.
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?
With 4 parameters, 0 required, no annotations, and no output schema, the description is too thin. It does not clarify the role of three of the four parameters, nor describe the return value format, which is significant for an agent to use the tool correctly.
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?
Although schema description coverage is 100%, the descriptions for url, host, and json are clearly copied from other tools (normalize/validate concerns) and are irrelevant or misleading for this timezone tool. The description adds no meaning beyond the zone parameter's existing IANA timezone name description, and it fails to clarify what url, host, and json do here.
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: 'Current time' + 'named IANA timezone'. This clearly conveys what the tool returns and is not a tautology. However, it does not distinguish itself from the sibling tool 'utc-time', which likely also returns current time, so some ambiguity remains.
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. In particular, the sibling 'utc-time' probably handles UTC, and the relationship between UTC time and named IANA zones is not addressed. The mismatched schema descriptions for url, host, and json further muddy usage.
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 time tools overlap heavily: timezone can replicate utc-time and tz-america-los-angeles, so an agent may struggle to pick the right one. The URL/HTTP tools are mostly distinct, but compatibility is vague and domain-shape/normalize-url both operate on hostname structure.
All tool names follow a consistent lowercase hyphenated style, which is clean and predictable. However, the semantic pattern is mixed: some names are verb-first (normalize-url, inspect-robots) while others are bare nouns (citation, timezone, utc-time), so it is not a strict verb_noun convention.
Eleven tools is not excessive in absolute terms, but the set is divided between time-related tools and unrelated URL/HTTP inspection utilities. Under the 'clock' identity, the count feels inflated and the purpose is diluted.
For a clock service, the core time queries are covered, but there is no timezone conversion or exhaustive zone listing. If viewed as a network-inspection suite, some exclusions are intentional, yet compatibility is underspecified and the overall domain remains unclear.