Skip to main content
Glama
API Colombia

API Colombia

by TernApp

TRM (dólar oficial en Colombia)

trm
Read-onlyIdempotent

Retrieve the official Colombian peso-per-dollar exchange rate for a specified date (defaults to today) to convert amounts or verify historical rates.

Instructions

Tasa Representativa del Mercado (pesos por dólar) vigente en una fecha, según la Superintendencia Financiera.

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

Input Schema

NameRequiredDescriptionDefault
fechaNoFecha AAAA-MM-DD (por defecto, hoy en Colombia)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful provenance ('según la Superintendencia Financiera'), which tells the agent the source is authoritative. However, it does not disclose the most relevant behavior for this tool: what happens on weekends/holidays or non-published dates (empty result? nearest prior rate? error?), nor the shape of the returned value beyond 'pesos por dólar'.

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, and the core resource is front-loaded before the source attribution. Every clause earns its place and nothing is padded or repeated from the title.

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?

For a one-optional-parameter read-only lookup this is close to adequate, and the annotations plus full schema coverage carry much of the burden. The gaps are the date-gap behavior (non-business days) and any hint of the return value, which matters because there is no output schema. An agent can call it, but may mis-handle empty or shifted results.

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?

There is a single parameter and schema description coverage is 100%, with the format (AAAA-MM-DD) and the 'today in Colombia' default both documented in the schema. The description only restates 'vigente en una fecha' and adds no format, timezone, or range guidance beyond that. Baseline 3 is appropriate when the schema does the work.

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?

The description names a precise, specific resource: the 'Tasa Representativa del Mercado (pesos por dólar)' in effect on a given date, with the issuing authority named. An agent immediately knows this returns an official FX rate rather than something else. It stops short of naming any sibling (e.g. 'indicadores', 'es_dia_habil') or stating what makes it distinct from them, so it is clear but not differentiating.

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

Usage Guidelines2/5

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

There is no when-to-use guidance and no exclusions: nothing tells the agent to call this instead of 'indicadores' when it needs a rate, nor that it should be combined with 'es_festivo'/'es_dia_habil' checks. The only usage hint anywhere is the schema default of today. Observing what to do for dates with no published rate is left entirely to inference.

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