Burs-IA Utils

Sumar días hábiles por país (93 países)

business-days-world

Read-onlyIdempotent

Suma o resta días hábiles a una fecha en uno de 93 países, saltando los festivos nacionales 2024-2030 (date-holidays) y el fin de semana del país (CLDR weekData: viernes-sábado en Egipto, Israel y Arabia Saudita, domingo en India, sábado-domingo en los demás), y lista los días saltados. Cuándo: hay que calcular un plazo en días hábiles en un país cuyos festivos y fin de semana el llamador no conoce. No para: sumar o restar días hábiles, saltando fines de semana y festivos dados (business-days-add). 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: Adds or subtracts business days to a date in one of 93 countries, skipping its national public holidays 2024-2030 (date-holidays) and its weekend (Unicode CLDR weekData: Friday-Saturday in Egypt, Israel and Saudi Arabia, Sunday in India, Saturday-Sunday… [EN completo / full EN: inputSchema.description]

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "days": 5,
      "country": "US",
      "start_date": "2026-11-20"
    },
    "name": "business-days-world"
  }
}

Input Schema

Name	Required	Description
`days`	Yes	Business days to add (negative subtracts) (integer; required; min -2000; max 2000).
`country`	Yes	Country: ISO 3166-1 alpha-2 (CO) or alpha-3 (COL) code, or name in English or Spanish (Colombia, Alemania, Germany) (string; required; at least 1 chars; up to 80 chars).
`start_date`	Yes	Start date (not counted) (YYYY-MM-DD) (string; required; at least 10 chars; up to 10 chars).

Output Schema

Name	Required	Description
`note`	No
`result`	No	any JSON value
`source`	No
`country`	No
`weekend`	No
`matched_by`	No
`start_date`	No
`weekday_en`	No
`weekday_es`	No
`business_days`	No
`calendar_days`	No
`country_name_en`	No
`country_name_es`	No
`skipped_holidays`	No
`skipped_weekend_days`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 4, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered; the description still adds real context: per-country weekend variations, holiday coverage window 2024-2030, that skipped days are listed, and concrete limits (64 KB input, 1 s, 1 MB result). It does not say what happens when start_date falls outside 2024-2030, which is the main remaining behavioral gap. 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.

Conciseness3/5

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

The Spanish block is well front-loaded (purpose, then when, then not-for, then side effects, determinism, limits). However the English portion is truncated mid-sentence with a pointer to inputSchema.description, effectively duplicating the same content twice and padding the definition 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?

An output schema exists, so return values need not be explained, and the description covers data sources, determinism, limits and the sibling alternative. The one missing piece is behavior for dates outside the supported 2024-2030 holiday window and for unsupported countries.

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 description coverage is 100%, and the schema already documents the country code formats, the days range (-2000 to 2000) and the YYYY-MM-DD start-date format, so the baseline is 3. The description adds only indirect constraints (holiday data only spans 2024-2030, weekend is country-derived) rather than parameter-specific syntax 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+resource (adds/subtracts business days to a date), the scope (93 countries), and the data sources behind it (date-holidays 2024-2030, CLDR weekData weekend rules). It also explicitly names the sibling it is not for (business-days-add), so an agent can tell the two 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?

Provides an explicit 'Cuándo' condition (a business-day deadline must be computed in a country whose holidays and weekend the caller does not know) and an explicit 'No para' exclusion routing to business-days-add when the caller supplies their own holidays. When-to-use, when-not-to-use and the alternative are all present.

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

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?