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 disclosure burden. It only says 'Current time in a named IANA timezone' and does not mention output format, behavior for invalid zone names, whether the operation is read-only, or any network/time-source dependencies.
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 wasted words. It communicates the core operation efficiently.
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 no output schema, no annotations, and a confusing four-parameter schema, the definition is not complete enough for an agent to invoke the tool correctly. The unrelated parameters and lack of parameter-selection guidance create a significant gap.
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 coverage is technically 100%, but the descriptions for url, host, and json are clearly unrelated to a timezone tool ('HTTPS URL to normalize or cite', 'JSON text to validate'). The description reinforces that zone is a timezone name but does not tell the agent whether the other parameters are ignored, optional, or invalid for this tool.
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 the current time for a named IANA timezone, which distinguishes it from siblings like utc-time and iana-zones. However, it is terse and does not clarify how the unrelated parameters in the input schema fit into this purpose.
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 intended use is implied: call this when you need the current time in a named IANA timezone. There is no explicit guidance about when to prefer utc-time or iana-zones, nor any exclusion criteria.
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.
Several tools operate on URLs (citation, compatibility, normalize-url, domain-shape, inspect-robots) and several on time (business-day, iana-zones, timezone, utc-time), creating some overlap in input types. The descriptions mostly clarify intent, but citation and compatibility in particular could still be confused.
Tool names mix nouns (citation, compatibility, timezone), verb phrases (inspect-robots, normalize-url, validate-json), and compound labels (business-day, iana-zones, utc-time). There is no consistent verb_noun or other naming pattern across the set.
Eleven tools is not excessive numerically, but the server name 'Weekday vs weekend' suggests a single narrow utility, while most tools are unrelated to that purpose. The set feels scattershot rather than deliberately scoped.
The tools span URL inspection, time/date, and JSON validation without a unifying domain, so there is no coherent capability surface to complete. Each mini-cluster has gaps, such as URL tools that only inspect and time tools that lack conversions or date arithmetic.