Skip to main content
Glama
API Colombia

API Colombia

by TernApp

Contar días hábiles entre dos fechas

contar_dias_habiles
Read-onlyIdempotent

Counts business days in Colombia between two dates, including how many days were holidays and weekends. Helps calculate working-day deadlines while optionally treating Saturdays as business days.

Instructions

Cuenta los días hábiles en Colombia desde el día siguiente a "desde" hasta "hasta" inclusive, e indica cuántos días fueron festivos y fines de semana.

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": {
      "desde": "<desde>",
      "hasta": "<hasta>"
    },
    "name": "contar_dias_habiles"
  }
}

Input Schema

NameRequiredDescriptionDefault
desdeYesFecha inicial AAAA-MM-DD
hastaYesFecha final AAAA-MM-DD
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

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is handled. The description earns credit for going beyond them: it discloses that the calculation uses the Colombian holiday calendar (the reason for openWorldHint), that the start date is exclusive, and that the result includes holiday and weekend counts.

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?

One dense sentence that front-loads the operation, then the exact interval semantics, then the returned breakdown. No filler, no restatement 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?

With no output schema, the description correctly compensates by naming what comes back (business days, holidays, weekend days). Combined with the exclusive-start rule and the Colombia calendar scope, an agent has what it needs; only the sabado_habil behavior is left entirely to the schema.

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?

Coverage is 100%, so the schema already documents all three parameters, but the description adds genuinely new meaning the schema lacks: that counting starts the day AFTER 'desde' rather than on it, which resolves the primary ambiguity of a date-range tool. The optional sabado_habil flag is left to the schema, which handles it adequately.

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 (cuenta), resource (días hábiles), jurisdiction (Colombia), and precise interval boundaries (from the day after 'desde' through 'hasta' inclusive). It also names the returned breakdowns (festivos, fines de semana). It does not explicitly differentiate itself from siblings like sumar_dias_habiles or es_dia_habil, which keeps it at 4.

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

Usage Guidelines3/5

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

The counting use case is implied clearly enough that an agent can guess it applies to measuring business days between two dates, but there is no explicit statement of when to prefer it over sumar_dias_habiles (add days) or es_dia_habil (test one date), nor any stated exclusions or prerequisites.

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