Skip to main content
Glama

Hora local en una ciudad

city-local-time
Read-only

Devuelve la fecha, la hora local, el desfase UTC y si rige el horario de verano en una ciudad dada por nombre (resuelta a su zona IANA con la lista GeoNames incluida), ahora o en un instante dado. Cuándo: un resultado de fechas, zonas horarias o calendario tiene que ser exacto (desfases, horario de verano, fines de mes, bisiestos). No para: devolver el instante actual (time-now). Efectos secundarios: ninguno (solo lectura, sin red, sin estado guardado). No determinista: según el reloj salvo que se dé at. Límites: entrada JSON de hasta 64 KB, 1 s por llamada, resultado de hasta 1 MB.

EN: Returns the local date, time, UTC offset and daylight-saving status in a city given by name (resolved to its IANA time zone from the embedded GeoNames list), now or at a given instant, with DST transitions from the runtime time-zone database. When: a date, time-zone or calendar result has to be exact (offsets, daylight saving, month ends, leap years). [EN completo / full EN: inputSchema.description]

Input Schema

NameRequiredDescriptionDefault
atNoInstant to use instead of the clock: ISO 8601 with Z/offset, or local time in the city (for tests and reproducible output) (string; optional; up to 40 chars).
cityYesCity name in its usual or Spanish form; a trailing ", country" narrows it (Medellín, Valencia, Venezuela, Nueva York) (string; required; at least 2 chars; up to 100 chars).
countryNoOptional country (ISO code or name) to tell apart cities with the same name (string; optional; at least 1 chars; up to 80 chars).

Output Schema

NameRequiredDescriptionDefault
utcNo
cityNo
dateNo
timeNo
offsetNo
sourceNo
timezoneNo
ambiguousNo
local_isoNo
weekday_enNo
weekday_esNo
dst_in_effectNo
other_matchesNo
offset_minutesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / city / examples
      Added value: +[
      +  "Bogotá"
      +]
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, openWorldHint=false and destructiveHint=false, and the description goes further: it discloses non-determinism (clock-dependent unless 'at' is supplied), no network/no stored state, and concrete limits (64 KB input, 1 s per call, 1 MB result). The non-determinism note is essential context 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?

The labeled sections (Cuándo / No para / Efectos secundarios / Límites) are front-loaded and scannable. It loses a point for presenting the same content in Spanish and then English and ending with a pointer to inputSchema.description, which is redundant padding.

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?

With a full output schema, complete parameter descriptions and annotations, the description covers everything else an agent needs: purpose, alternatives, determinism, side effects and hard limits. Nothing required for a correct call is missing.

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

Parameters3/5

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

Schema coverage is 100% and each parameter (city, country, at) is fully documented in the schema, so the baseline is 3. The description adds behavioral color about how 'city' is resolved and that 'at' makes output reproducible, but no additional syntax or format detail beyond the schema.

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 plus the exact return payload (local date, time, UTC offset, DST status) and how the city is resolved (IANA zone via embedded GeoNames). It explicitly contrasts with the sibling time-now, so an agent can tell them apart without opening either schema.

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?

Contains explicit 'Cuándo' guidance (when a date/time-zone/calendar result must be exact, including month ends and leap years) and an explicit 'No para' exclusion naming time-now as the alternative. Nothing is left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources