Skip to main content
Glama

UVT ↔ pesos (Colombia)

co-uvt-convert
Read-onlyIdempotent

Convierte entre UVT y pesos para 2024 ($47.065), 2025 ($49.799) o 2026 ($52.374, Resolución DIAN 000238 de 2025). Cuándo: hay que aplicar con exactitud una regla colombiana (DIAN, festivos de la Ley Emiliani, montos en COP, IVA, GMF, UVT), p. ej. al facturar o cobrar. No para: formatear un valor en pesos colombianos (co-cop-format). Efectos secundarios: ninguno (solo lectura, sin red, sin estado guardado). Determinista: la misma entrada da la misma salida. Límites: entrada JSON de hasta 64 KB, 1 s por llamada, resultado de hasta 1 MB.

EN: Converts between UVT (Unidad de Valor Tributario) and Colombian pesos for 2024 ($47.065), 2025 ($49.799) or 2026 ($52.374, DIAN Resolución 000238 de 2025). When: a Colombian rule (DIAN, Ley Emiliani holidays, COP amounts, IVA, GMF, UVT) has to be applied exactly, e.g. in invoicing or payment flows. Not for: formatting an amount as Colombian pesos the way it is written in Colombia (co-cop-format). [EN completo / full EN: inputSchema.description]

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "uvt": 350
    },
    "name": "co-uvt-convert"
  }
}

Input Schema

NameRequiredDescriptionDefault
uvtNoAmount in UVT (number; optional; min 0; max 1000000000).
yearNoTax year (integer; optional; default 2026; min 2024; max 2026).
pesosNoAmount in pesos (number; optional; min 0; max 1000000000000000).

Output Schema

NameRequiredDescriptionDefault
uvtNo
yearNo
pesosNo
uvt_valueNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "uvt": 350
      +  }
      +]
  2. Changed1 schema field changed
    • addedInput schema / description
      Added value: +"EN: Converts between UVT (Unidad de Valor Tributario) and Colombian pesos for 2024 ($47.065), 2025 ($49.799) or 2026 ($52.374, DIAN Resolución 000238 de 2025). When: a Colombian rule (DIAN, Ley Emiliani holidays, COP amounts, IVA, GMF, UVT) has to be applied exactly, e.g. in invoicing or payment flows. Not for: formatting an amount as Colombian pesos the way it is written in Colombia (co-cop-format). Side effects: none (read-only, no network access, no stored state). Deterministic: the same input gives the same output. Limits: JSON input up to 64 KB, 1 s per call, result up to 1 MB."
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds real value beyond them: explicit size and timing limits (64 KB input, 1 s per call, 1 MB result) and a restatement of no-network/no-stored-state and determinism. It does not say what happens on conflicting or absent inputs, which keeps it below 5.

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?

Front-loads the conversion statement before usage, exclusions, effects and limits, and the labeled segments (Cuándo / No para / Efectos secundarios / Determinista / Límites) make it scannable. It loses a point for shipping the same content twice in Spanish and English while also deferring full EN to inputSchema.description, which is redundant bulk.

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?

An output schema exists, so return values need no explanation, and annotations plus schema cover safety and every parameter. The description fills the remaining gaps an agent needs — supported years with their UVT values, exactness of purpose, the sibling exclusion, and operational limits. Only the uvt-vs-pesos exclusivity is unstated, a minor omission for an otherwise complete definition.

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% with all three parameters documented including defaults and min/max, so the baseline is 3. The description adds the per-year UVT conversion values, which is useful context not in the schema, but it never states the central semantic rule that uvt and pesos are alternative directions of the same conversion (supply one, not both) — a gap the schema alone also does not fill.

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?

States a specific verb and resource (converts between UVT and Colombian pesos), pins the exact domain values per year ($47.065 / $49.799 / $52.374 with the DIAN resolution cited), and explicitly contrasts itself with the sibling co-cop-format. An agent can distinguish it from co-cop-parse, co-iva and co-gmf without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Uses explicit labeled sections: 'Cuándo' gives the triggering condition (applying a Colombian rule exactly, e.g. invoicing or payment flows) and 'No para' names the alternative tool co-cop-format plus the condition that selects it. Both when-to-use and when-not-to-use are stated, leaving nothing to inference.

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