Skip to main content
Glama
API Colombia

API Colombia

by TernApp

Convertir UVT ↔ pesos

convertir_uvt
Read-onlyIdempotent

Convert UVT to Colombian pesos or pesos to UVT using the selected year's value; provide exactly one amount, either UVT or pesos.

Instructions

Convierte UVT a pesos colombianos o pesos a UVT con el valor del año. Envía exactamente uno: "uvt" o "pesos".

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

Input Schema

NameRequiredDescriptionDefault
uvtNoCantidad en UVT
anioNoAño (por defecto, el año actual en Colombia)
pesosNoCantidad en pesos colombianos

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is fully covered. The description adds that the rate is year-dependent ('con el valor del año'), which is useful context, but it does not state the failure behavior when neither or both amounts are supplied.

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 short sentences with zero filler: the conversion behavior first, the input constraint second. Nothing could be removed without losing information.

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

Completeness3/5

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

There is no output schema, so the description carries the burden of describing what comes back, and it never says what the result looks like (converted amount, the UVT value used, error shape). For a simple two-mode converter this is an adequate but incomplete definition.

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?

Schema coverage is 100% and each parameter is documented, so baseline would be 3. The description earns an extra point by imposing a mutual-exclusivity constraint that the schema itself does not encode (no oneOf/anyOf present), which meaningfully constrains how the parameters are supplied.

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 ('Convierte') and both resources/directions ('UVT a pesos colombianos o pesos a UVT'), plus the governing factor ('con el valor del año'). An agent can immediately tell this apart from siblings like 'trm' or 'indicadores' without opening the schema.

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?

Gives an explicit selection rule for the two modes: send exactly one of 'uvt' or 'pesos'. That is actionable usage guidance, but it says nothing about when this conversion is preferable to related tools (e.g., TRM) or what happens if the rule is violated.

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