Skip to main content
Glama
API Colombia

API Colombia

by TernApp

¿Es festivo?

es_festivo
Read-onlyIdempotent

Check whether a given date is a public holiday in Colombia and identify which holiday it is.

Instructions

Indica si una fecha es festivo en Colombia y cuál.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "es_festivo"
  }
}

Input Schema

NameRequiredDescriptionDefault
fechaNoFecha AAAA-MM-DD (por defecto, hoy en Colombia)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=true, so the safety and external-lookup profile is covered structurally. The description adds one piece of behavioral value by saying it also returns which holiday it is, but says nothing about the source calendar, time zone handling, or behavior when the request is served for a date outside a known year — notable given openWorldHint=true.

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?

A single front-loaded sentence with no redundant wording; the geography qualifier is placed well. It is lean to the point of omitting return-shape detail, but there is no filler to cut.

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 one-optional-parameter, read-only query with full schema coverage and complete annotations, the description covers the essentials. The main gap is that no output schema exists and the description only gestures at the return value ("y cuál"), without indicating whether the holiday name, a boolean, or both are returned.

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 single parameter (fecha, AAAA-MM-DD, defaulting to today in Colombia) is fully documented in the schema. The description adds only the 'en Colombia' scope, which subtly tells the agent which calendar the date is interpreted against. Baseline 3 applies.

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?

"Indica si una fecha es festivo en Colombia y cuál" states a specific verb (indicate) and a specific resource (whether a date is a holiday, and which one), and adds geographic scope (Colombia). It does not, however, distinguish itself from the sibling tools es_dia_habil or festivos, so an agent cannot route between them from the description alone.

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

Usage Guidelines2/5

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

There is no when-to-use guidance: no mention of when to prefer this over es_dia_habil (business-day check) or festivos (presumably a holiday listing), and no prerequisites or exclusions. Usage is only implied by the name and the single date parameter.

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