Skip to main content
Glama
API Colombia

API Colombia

by TernApp

Obligaciones DIAN soportadas

obligaciones_dian
Read-onlyIdempotent

Lists 18 Colombian national tax obligations, including which NIT digits determine each one and its legal basis, to help identify applicable DIAN requirements.

Instructions

Lista las 18 obligaciones tributarias nacionales soportadas, de qué dígitos del NIT dependen y su base legal.

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": "obligaciones_dian"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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 a read-only, idempotent, non-destructive, open-world operation, so the safety profile is covered. The description adds value beyond them by stating what the response contains: the 18 obligations, their NIT-digit dependency, and their legal basis — useful disclosure given there is no output schema.

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?

A single sentence with no filler, front-loaded with the core resource and followed by the two value facets. Every clause earns its place.

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 zero-argument, no-output-schema lookup tool, the description supplies the essentials: what is listed and what fields come back. Minor gaps remain, such as whether the result is static or paginated, but the low complexity means little more is required.

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?

The tool takes zero parameters, which is the baseline-4 case; there is nothing for the description to disambiguate. The empty schema matches the argument-free nature of the call.

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?

Uses a specific verb ("Lista") plus a precise resource ("18 obligaciones tributarias nacionales soportadas") and enumerates the returned facets (NIT digit dependency, legal basis). It implicitly separates itself from calendar/deadline siblings like calendario_dian or vencimientos_dian, though it never names an alternative explicitly.

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?

Usage is only implied: an agent can infer it should call this to discover which obligations exist before querying deadlines. There is no explicit when-to-use, when-not-to-use, or named alternative among the sibling tools.

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