Skip to main content
Glama
API Colombia

API Colombia

by TernApp

Próximos vencimientos DIAN de un NIT

vencimientos_dian
Read-onlyIdempotent

Retrieve upcoming Colombian DIAN tax deadlines for a NIT or cédula by selected obligations, ordered by date with days remaining, so users know what is due and when to file.

Instructions

Devuelve los próximos vencimientos tributarios nacionales de la DIAN (Colombia) para un NIT o cédula, ordenados por fecha y con los días que faltan. Úsala cuando pregunten "¿qué le vence a este NIT?", "¿cuándo debo declarar renta?" o "¿cuándo vence la retención/IVA?". Colombian DIAN tax deadlines by taxpayer ID.

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

Input Schema

NameRequiredDescriptionDefault
nitYesNIT o cédula, con o sin dígito de verificación (ej. 900123456-8)
diasNoDías hacia adelante (por defecto 60)
desdeNoFecha inicial AAAA-MM-DD (por defecto, hoy en Colombia)
obligacionesYesObligaciones del contribuyente. Ej.: persona natural → ["renta_personas_naturales"]; empresa del régimen ordinario → ["renta_personas_juridicas","retencion_fuente","iva_bimestral"]

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 open-world behavior, so the safety profile is covered. The description still adds meaningful context beyond them: results are national-scope DIAN deadlines, sorted by date, each with days remaining. It stops short of describing pagination or coverage limits if some obligations have no computed deadline.

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?

The core purpose and trigger examples are front-loaded in efficient Spanish prose. The trailing English fragment "Colombian DIAN tax deadlines by taxpayer ID" merely duplicates the opening sentence and adds no new information, which is the only real waste.

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 four parameters, full schema coverage, no output schema and no nesting, the key remaining burden is explaining what comes back, and the description does state the list is date-ordered with days remaining. What is missing is edge-case behavior, e.g. what happens when an obligation has no upcoming deadline within the window.

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 nit, desde, dias and obligaciones are already documented, including the NIT/cédula format and example obligation sets. The description only restates that the identifier may be a NIT or cédula and adds no format or constraint detail the schema lacks; 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?

"Devuelve los próximos vencimientos tributarios nacionales de la DIAN (Colombia) para un NIT o cédula" gives a specific verb, resource and scope, and adds ordering (by date) and derived output (days remaining). It is clear what the tool returns, but it never names or contrasts a sibling such as calendario_dian or obligaciones_dian, so the agent must infer the boundary.

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?

The explicit trigger phrases ("¿qué le vence a este NIT?", "¿cuándo debo declarar renta?", "¿cuándo vence la retención/IVA?") give the agent concrete when-to-use conditions. There is no when-not guidance or pointer to an alternative tool when the user only needs a generic calendar or a list of obligations.

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