Burs-IA Utils

Lista de zonas horarias IANA

timezone-list

Read-onlyIdempotent

Lista las zonas horarias IANA soportadas, con filtro opcional. Cuándo: un resultado de fechas, zonas horarias o calendario tiene que ser exacto (desfases, horario de verano, fines de mes, bisiestos). No para: convertir una fecha/hora de una zona horaria IANA a otra, considerando horario de verano (timezone-shift). Efectos secundarios: ninguno (solo lectura, sin red, sin estado guardado). Determinista: la misma entrada da la misma salida. Límites: entrada JSON de hasta 64 KB, 1 s por llamada, resultado de hasta 1 MB.

EN: Lists the IANA time zone identifiers supported by this runtime, optionally filtered by a case-insensitive substring (e.g. America, Bogota). When: a date, time-zone or calendar result has to be exact (offsets, daylight saving, month ends, leap years). Not for: converting a wall-clock date-time from one IANA time zone to another (timezone-shift). Side effects: none (read-only, no network access, no stored state). [EN completo / full EN: inputSchema.description]

Input Schema

Name	Required	Description	Default
`filter`	No	Substring filter (string; optional; default ""; up to 64 chars).

Output Schema

Name	Required	Description	Default
`count`	No
`timezones`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 1, 2026

addedInput schema / description

Added value: +"EN: Lists the IANA time zone identifiers supported by this runtime, optionally filtered by a case-insensitive substring (e.g. America, Bogota). When: a date, time-zone or calendar result has to be exact (offsets, daylight saving, month ends, leap years). Not for: converting a wall-clock date-time from one IANA time zone to another (timezone-shift). Side effects: none (read-only, no network access, no stored state). Deterministic: the same input gives the same output. Limits: JSON input up to 64 KB, 1 s per call, result up to 1 MB."

First observedNov 1, 2026

TDQS

A4.8/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false and openWorldHint=false; the description goes beyond them by stating no network access, no stored state, determinism of output, and concrete limits (64 KB input, 1 s per call, 1 MB result). These are operational facts an agent cannot get from the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well front-loaded with labeled sections (When / Not for / Side effects / Deterministic / Limits) and a one-line summary. It loses a point for the Spanish-then-English duplication and the trailing pointer to inputSchema.description, which restates content already present in the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single optional-parameter, read-only list tool with an output schema (so return shape need not be described), the definition covers purpose, routing, side effects, determinism and size/time limits — nothing needed to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds two things the schema omits: the filter is case-insensitive and illustrative values (America, Bogota) that clarify it matches IANA identifiers rather than arbitrary text. It does not clarify whether matching applies to the full path or any segment.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("lista las zonas horarias IANA soportadas") plus the exact scope of the optional filtering. The sibling landscape is dense with timezone tools (timezone-shift, timezone-info, timezone-overlap) and the description names the one it is not.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit "Cuándo" trigger (when a date/timezone/calendar result must be exact: offsets, DST, month ends, leap years) and explicit "No para" exclusion naming timezone-shift as the alternative for conversions. Nothing is left to inference about when to pick this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Burs-IA Utils tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?