Common IANA timezone names for clock calls.
| 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 provided, the description carries the full burden of disclosing behavior, but it does not state side effects, read-only status, error handling, or what happens with invalid input. The description implies a read-only lookup but never confirms it.
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 concise sentence, which is efficient, but its structure fails to align with the parameter list, making it confusing rather than clarifying. It lacks any mapping between the stated purpose and the actual inputs.
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 severe mismatch between the description and the parameters, the tool definition is not coherent enough for an agent to use correctly. The absence of an output schema and any parameter explanation compounds the incompleteness, leaving critical information missing.
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 parameters (url, host, json, zone) are completely disconnected from the stated purpose of providing IANA timezone names. The schema descriptions for url and json appear copied from unrelated tools (normalize-url and validate-json), and the description offers no explanation of how any parameter relates to timezone lookup, leaving the agent unable to construct a valid call.
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 the tool provides 'Common IANA timezone names for clock calls,' which gives a general sense of purpose but remains vague about whether it returns a list, validates a name, or resolves an alias. It does not clearly specify the tool's core function or output, leaving the agent to guess.
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 offers no explicit guidance on when to use this tool versus its siblings like 'timezone' or 'utc-time.' It only loosely ties the tool to 'clock calls' without explaining distinct scenarios or fallback conditions, leaving the agent without decision 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.
Tools are mostly distinct, but 'compatibility' is vague and 'citation' vs 'normalize-url' both deal with URLs, though with different purposes. Overall, descriptions help clarify intent.
Names follow a consistent lowercase hyphenated pattern (e.g., normalize-url, validate-json) with a few single-word exceptions like 'citation' and 'timezone'. The style is predictable and readable.
11 tools is well within the typical range for a general-purpose utility server, covering URL, time, HTTP status, JSON, and language helpers without being excessive.
The tool set covers a broad range of common web and time utilities. Minor gaps like DNS lookup or IP info exist, but for the apparent scope, the coverage is solid.