Skip to main content
Glama
API Colombia

API Colombia

by TernApp

Calendario tributario DIAN del año

calendario_dian
Read-onlyIdempotent

Look up Colombian DIAN tax deadlines by year and obligation, using the last one or two NIT digits to find dates. Request only needed obligations to keep responses concise.

Instructions

Calendario tributario nacional de la DIAN para un año: fechas de cada obligación según el último dígito (o los dos últimos, en renta de personas naturales) del NIT. Pide solo las obligaciones necesarias: la respuesta completa es larga.

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": {
      "obligaciones": "<obligaciones>"
    },
    "name": "calendario_dian"
  }
}

Input Schema

NameRequiredDescriptionDefault
anioNoAño (por defecto, el año actual en Colombia)
obligacionesYesObligaciones a consultar

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

The description adds domain context the annotations cannot: that the schedule is keyed to the NIT's last digit (or last two for natural-person income tax) and that a full response is large, implying a cost to broad requests. Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered; the missing piece is what the response items look like.

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?

Two sentences, both earning their place: the first defines scope and the keying rule, the second delivers the actionable caution about response size. Front-loaded with the purpose, zero redundancy.

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 read-only tool with no output schema and full schema coverage, the description supplies purpose, the NIT-digit grouping, and a size warning. It stops short of describing the shape of each returned date entry, which is the main residual gap.

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 coverage is 100% – both parameters carry descriptions, including the default-to-current-Colombian-year behavior for anio and the obligation list for obligaciones. The description reinforces the obligation-narrowing advice and explains the NIT-digit basis for the returned dates, but adds little parameter-level detail beyond the schema.

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 resource (calendario tributario nacional DIAN) with a clear verb implied (consulta de fechas) and the grouping rule (último dígito del NIT, dos en renta de personas naturales). It is clear what the tool returns and how results are organized, though it never names the sibling tools (vencimientos_dian, obligaciones_dian) it could be confused with.

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?

Offers one concrete usage rule: 'Pide solo las obligaciones necesarias: la respuesta completa es larga', which steers the agent to narrow the request. It gives no explicit when-to-use vs. when-not-to-use, and does not point to an alternative tool for a single obligation lookup or for non-annual queries.

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