Skip to main content
Glama
API Colombia

API Colombia

by TernApp

¿Es día hábil?

es_dia_habil
Read-onlyIdempotent

Checks whether a given date is a business day in Colombia and explains why not, such as weekend or public holiday; optionally treats Saturdays as working days.

Instructions

Indica si una fecha es día hábil en Colombia y, si no lo es, por qué (sábado, domingo o festivo).

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_dia_habil"
  }
}

Input Schema

NameRequiredDescriptionDefault
fechaNoFecha 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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuine value by disclosing what the result contains when the answer is negative (the reason: Saturday, Sunday, or holiday), but says nothing about calendar sourcing, timezone handling beyond 'Colombia', or behavior on malformed input.

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 sentence, front-loaded with the core question and followed by the useful qualifier about the reason for a negative answer. Nothing is redundant or padded.

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 two-parameter, zero-required read-only query with no output schema, the description covers the essential behavior, including what the response conveys. A brief note on invalid-date handling or the holiday calendar source would make it fully complete.

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 both parameters including the non-obvious sabado_habil flag are already documented in structured form. The description only reinforces the Colombia scope and does not elaborate on how sabado_habil changes the outcome, so it stays at the baseline for schema-covered parameters.

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?

The description states a specific verb and resource ('Indica si una fecha es día hábil en Colombia') and scopes it geographically, which is far more than a restatement of the name. It also adds the diagnostic angle ('por qué: sábado, domingo o festivo'), which implicitly separates it from a pure holiday checker like es_festivo, though it 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 Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance and no mention of the related tools (es_festivo, contar_dias_habiles, sumar_dias_habiles) that an agent would need to choose between. The purpose statement hints at the use case, but the agent must infer the routing decision entirely on its own.

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