list_zonesReturn all IANA timezone names supported by TimeAPI.io. Use as a directory to find valid timeZone strings for other calls.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Input schema / examplesAdded value: +[
+ {}
+]Output schema / (root)Previous value: -nullNew value: +{
+ "description": "List of supported timezones",
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and non-destructive nature. The description adds that it returns supported IANA names, which is useful context for behavior beyond 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?
Two concise sentences with no wasted words, efficiently communicating purpose and usage.
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?
For a zero-parameter list tool with an output schema, the description sufficiently explains what the tool returns and how to use it, completing the context.
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?
No parameters exist, so the baseline is 4. The description does not need to add parameter info and simply states the output.
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 it returns all IANA timezone names supported by TimeAPI.io, distinguishing it from sibling tools by specifying it's a directory for valid timeZone strings.
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?
Explicitly says 'Use as a directory to find valid timeZone strings for other calls,' providing both when-to-use and implied when-not-to-use guidance.
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 overlap heavily: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all answer natural-language data questions, and ask_pipeworx_beta is explicitly identical to ask_pipeworx right now. The current_time* variants and multiple Polymarket scanners also create real selection ambiguity, though the memory and subscription tools are clearly distinct.
Names are mostly lowercase snake_case and readable, but there is no consistent verb_noun pattern: some are imperative (ask_pipeworx, compare_entities, generate_llms_txt) while others are object-first (entity_profile, recent_changes, pipeworx_trending). Subfamilies like current_time* and polymarket_* are internally consistent, but the overall set follows no predictable convention.
Forty tools is far too many for a server named Timeapi Io; only about nine tools actually relate to time zones and current time. The rest form a sprawling Pipeworx research, prediction-market, memory, and subscription platform, making this a mega-bundle rather than a well-scoped toolset.
The time-related surface covers current time, zone conversion, zone metadata, and ISO parsing, but lacks common date math or general formatting operations. The Pipeworx side is quite complete for research and fact-checking, but the mixed domain makes coverage uneven and hard to reason about as a single coherent service.