Skip to main content
Glama
API Colombia

API Colombia

by TernApp

UVT, salario mínimo y auxilio de transporte

indicadores
Read-onlyIdempotent

Retrieves official Colombian UVT, minimum wage (SMMLV), and transport allowance values for a chosen year from 2019 onward, defaulting to the current year.

Instructions

Valor de la UVT, el salario mínimo (SMMLV) y el auxilio de transporte en Colombia para un año (2019 en adelante).

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

Input Schema

NameRequiredDescriptionDefault
anioNoAño (por defecto, el año actual en Colombia)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds that the supported range starts in 2019, which is useful behavior beyond the annotations, but says nothing about the shape of the returned data or what happens outside the range.

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?

One front-loaded sentence with no filler, and the three returned values are enumerated first. Slight density but nothing extraneous.

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 one-optional-parameter read-only lookup with full annotations and no output schema, the description covers what is returned and the valid year range. Only the return shape (one record per year, units) is left implicit, which is a minor gap.

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 optional parameter already fully documented in the schema (description plus min/max bounds). The description merely restates the 2019 floor, adding no syntax or default behavior detail beyond what the schema provides, so the schema-coverage baseline of 3 applies.

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?

Names the three concrete values returned (UVT, salario mínimo, auxilio de transporte), the country (Colombia), and the supported year range (2019 onward). This clearly separates it from a sibling like convertir_uvt, 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?

The context of use is implied by the returned values, but there is no explicit guidance on when to pick this tool over siblings such as trm or convertir_uvt, nor an exclusion statement. For a simple lookup this is adequate but thin.

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