Skip to main content
Glama
API Colombia

API Colombia

by TernApp

Sumar o restar días hábiles

sumar_dias_habiles
Read-onlyIdempotent

Calculate a date by adding or subtracting Colombian business days, skipping weekends and holidays, to determine legal deadlines, delivery dates, or the result of N business days after a start date.

Instructions

Calcula la fecha que resulta de sumar (o restar, con números negativos) días hábiles en Colombia, saltando fines de semana y festivos. El conteo empieza el día siguiente a la fecha inicial. Úsala para plazos legales, entregas o "¿qué fecha es N días hábiles después de…?".

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "dias": "<dias>"
    },
    "name": "sumar_dias_habiles"
  }
}

Input Schema

NameRequiredDescriptionDefault
diasYesDías hábiles a sumar (negativo para restar)
fechaNoFecha inicial AAAA-MM-DD (por defecto, hoy en Colombia)
sabado_habilNotrue si el sábado cuenta como día hábil (algunos sectores laborales). Por defecto false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety bar is low; the description still adds a genuinely non-obvious behavioral rule: counting starts the day AFTER the initial date. It also discloses that weekends and Colombian holidays are skipped, which an agent could not infer from annotations alone.

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

Conciseness5/5

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

Three short sentences, front-loaded with the core computation, then the counting rule, then the use cases. No filler or repetition of the title.

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?

For a single-computation tool with full schema coverage and annotations covering the safety profile, this is nearly complete; the counting-offset rule is the key detail an agent needs. The one gap is that it never states the return shape (a YYYY-MM-DD date string) and there is no output schema to cover it.

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%, so all three parameters are already documented in the schema. The description reinforces the negative-number semantics for subtraction but says nothing about sabado_habil or the default-to-today behavior, adding little beyond the structured fields.

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

Purpose4/5

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

States a specific verb and result ('Calcula la fecha que resulta de sumar/restar días hábiles en Colombia') and clarifies the domain calendar being used. It implicitly separates itself from contar_dias_habiles by returning a date rather than a count, but never names a sibling explicitly.

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

Usage Guidelines4/5

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

Gives concrete use contexts ('plazos legales, entregas, ¿qué fecha es N días hábiles después de…?') that make the when-to-use condition clear. It stops short of stating when NOT to use it or naming contar_dias_habiles / festivos as the alternatives for adjacent questions.

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