Burs-IA Utils

Horario laboral común entre zonas

timezone-overlap

Read-onlyIdempotent

Encuentra, para una fecha y varias zonas horarias con su horario laboral, la franja en que todos coinciden. Cuándo: un resultado de fechas, zonas horarias o calendario tiene que ser exacto (desfases, horario de verano, fines de mes, bisiestos). No para: listar las zonas horarias IANA soportadas (timezone-list). 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: Finds, for a date and a list of time zones with local working hours, the UTC window when everyone is within working hours, shown in each zone's local time. When: a date, time-zone or calendar result has to be exact (offsets, daylight saving, month ends, leap years). Not for: listing the supported IANA time zones (timezone-list). Side effects: none (read-only, no network access, no stored state). Deterministic: the same input gives the same output. [EN completo / full EN: inputSchema.description]

Input Schema

Name	Required	Description	Default
`date`	Yes	Date YYYY-MM-DD (string; required; up to 10 chars; format date).
`zones`	Yes	Participants (array of object; required; at least 1 items; up to 20 items).

Output Schema

Name	Required	Description	Default
`local`	No
`minutes`	No
`overlap`	No
`utc_end`	No
`utc_start`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 2, 2026

addedInput schema / properties / date / examples
```
Added value: +[
+  "2026-11-03"
+]
```

addedInput schema / properties / zones / examples

Added value: +[
+  [
+    {
+      "timezone": "America/Bogota"
+    },
+    {
+      "timezone": "Europe/Madrid"
+    }
+  ]
+]

Changed1 schema field changedNov 1, 2026

addedInput schema / description

Added value: +"EN: Finds, for a date and a list of time zones with local working hours, the UTC window when everyone is within working hours, shown in each zone's local time. When: a date, time-zone or calendar result has to be exact (offsets, daylight saving, month ends, leap years). Not for: listing the supported IANA time zones (timezone-list). 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.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, yet the description still adds real value: determinism guarantee, no network access, no stored state, and concrete limits (64 KB input, 1 s per call, 1 MB result). It does not say what happens when no common window exists, which is the one behavioral gap.

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?

Purpose is front-loaded and the labeled sections (Cuándo / No para / Efectos / Determinista / Límites) make it scannable. The cost is full duplication in Spanish and English within the same description, which roughly doubles length without adding information.

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

Completeness4/5

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

With an output schema present, return values need not be described, and annotations plus the description cover safety, limits and routing. The only missing piece an agent would want is edge-case behavior (no overlap, DST transition day, start after end), which the description leaves silent.

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%, so date, timezone, start and end are already documented with formats, defaults and patterns. The description adds conceptual framing (each zone carries its own working hours, result shown in each zone's local time) but no per-parameter detail beyond the schema, so the baseline 3 applies.

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: finds the UTC window where all listed time zones are simultaneously within their local working hours, for a given date. It explicitly distinguishes itself from timezone-list, so an agent can route correctly 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?

Has an explicit 'When:' clause (any date/time-zone/calendar result that must be exact: offsets, DST, month ends, leap years) and an explicit 'No para:' clause naming the sibling timezone-list for the excluded case. Both the positive and negative conditions are stated.

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?