list_timezonesList all 590+ IANA timezone strings available from timeapi.io.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| timezones | Yes | List of all available IANA timezone strings |
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?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds value by specifying the exact data source (timeapi.io) and the count of timezones (590+), which reflects the tool's scope and potential size of response. No contradiction with annotations.
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 that front-loads the verb and resource, followed by a valuable qualifier ('590+', 'from timeapi.io'). Every word contributes meaning, and there is no redundancy or irrelevant detail.
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?
The tool is extremely simple with no parameters, rich annotations, and an output schema (though not shown). The description provides the essential context: what is listed, the source, and the approximate size. Nothing critical is missing, and the description fully suffices for an agent to select and invoke 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?
The tool has zero parameters, so the baseline score is 4. The description does not need to elaborate on parameters, and the schema already reflects an empty parameter set. No additional parameter meaning is required.
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 lists all 590+ IANA timezone strings from timeapi.io, using a specific verb ('List') and resource ('timezone strings'). This unambiguously distinguishes it from sibling time-related tools like get_time_by_timezone or convert_time, which perform different operations.
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 usage context: use when you need a comprehensive list of IANA timezones. It does not explicitly mention when not to use or name alternatives, but given the tool's simplicity (zero parameters), the context is clear enough. The '590+' detail suggests it's the definitive source for supported timezones.
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.
Many tools have overlapping purposes, especially the multiple 'ask_pipeworx' variants and several Polymarket utilities. The server mixes a few timezone tools with a large collection of unrelated data lookup and analysis tools, making it hard for an agent to distinguish which tool to use for a given task.
While all tool names use snake_case, the verbs are highly inconsistent (e.g., 'ask_pipeworx', 'convert_time', 'discover_tools', 'validate_claim'). There is no clear pattern or predictable naming convention across the set.
The server name 'timezone' suggests a narrow domain, but it contains 35 tools, the vast majority of which are unrelated to timezones. This is far too many for the implied scope, and the server seems to be a dumping ground for various services.
For a timezone server, only 4 tools (convert_time, get_time_by_ip, get_time_by_timezone, list_timezones) are relevant. Critical timezone functionality like time zone conversions with arbitrary offsets, DST handling, or time zone by coordinates is missing. The remaining tools are completely unrelated to the server's stated purpose.