Skip to main content
Glama

Validate Colombia NIT (tax ID)

validate_colombia_nit
Read-onlyIdempotent

Validate a Colombian NIT with the DIAN check-digit algorithm and look it up live in the RUES commercial registry kept by the chambers of commerce (Confecámaras open data on datos.gov.co, licensed CC BY-SA 4.0). Returns the computed check digit, legal name, registration status (active, cancelled and others), last renewal year, registration dates, chamber of commerce, legal form, CIIU activity codes and a pass/review/fail assessment with reasons. This is the commercial registry, not DIAN tax status. For individuals only the check digit and registration status are returned, without name or address.

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>"
    },
    "name": "validate_colombia_nit"
  }
}

Input Schema

NameRequiredDescriptionDefault
nitYesColombian NIT with or without the check digit, e.g. "899999068-1" or "899999068". Dots and spaces are ignored.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / nit / description
      Previous value: -"Colombian NIT with or without the check digit, e.g. \"860002964-4\" or \"860002964\". Dots and spaces are ignored."New value: +"Colombian NIT with or without the check digit, e.g. \"899999068-1\" or \"899999068\". Dots and spaces are ignored."
  2. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive and open-world, so the safety profile is known; the description adds the data source and license, the pass/review/fail assessment model, and the important caveat that individuals return only check digit and status without name or address. It stops short of describing failure behavior (NIT not found, registry downtime) or latency/rate considerations.

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?

Front-loaded with the core action and data source, then the returns, then the critical scope exclusion. Every sentence carries information the agent needs, and the enumerated return fields compensate for the absent output schema rather than padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With only one parameter, an output schema absent, and annotations carrying the safety profile, the description closes the remaining gaps by enumerating return fields and stating the individual-person limitation. An agent has enough to call it and interpret the result without opening anything else.

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% and the single parameter's description already covers the accepted formats, check-digit optionality, and ignoring of dots and spaces. The tool description adds nothing further about the nit parameter, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb+resource (validate a Colombian NIT) and pins down exactly which algorithm and registry are used (DIAN check digit plus the RUES/Confecámaras commercial registry). It explicitly distinguishes its scope from DIAN tax status, so an agent can separate it from the format-only sibling validators.

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 implied by the scope statements ('This is the commercial registry, not DIAN tax status') and by the note on what individuals return, which helps an agent decide whether the lookup is appropriate. However, it never names an alternative such as validate_tax_id_format for an offline/format-only check, and gives no explicit when-not conditions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources