Skip to main content
Glama

UMA, salario mínimo e ISR

constantes
Read-onlyIdempotent

Retrieves official Mexican UMA, minimum wage, and ISR values by year, date, or period, including the DOF publication that supports each amount.

Instructions

UMA, salario mínimo y tarifas de ISR publicados en el DOF, cada uno con la publicación que lo respalda. tipo uma con anio (la UMA de ese año) o con fecha (la vigente ese día: cada UMA rige del 1 de febrero al 31 de enero siguiente); tipo salario_minimo con anio (zona general y Zona Libre de la Frontera Norte); tipo isr con periodo (mensual o anual) y anio. Los montos son texto con dos decimales. Consulta la API de MéxicoAPI (la pública, o la de MEXICOAPI_BASE) y, si no responde, usa los datos del paquete y lo advierte. Con MEXICOAPI_SIN_RED=1 responde con los datos del paquete, sin red.

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": {
      "tipo": "<tipo>"
    },
    "name": "constantes"
  }
}

Input Schema

NameRequiredDescriptionDefault
anioNoAño de 4 cifras.
tipoYes
fechaNoSolo con tipo uma: día en que se busca la vigente.
periodoNoSolo con tipo isr.

Output Schema

NameRequiredDescriptionDefault
tipoYes
as_ofYesFecha de corte del dataset: la de la última actualización que lo cambió (en los datos curados, la publicación más reciente de sus fuentes). No es la fecha del valor, que va en datos.
datosYesLa UMA (objeto), el salario mínimo (lista, uno por zona) o la tarifa de ISR (objeto con sus tramos), según tipo. Cada uno trae su fuente.
avisosYesLas advertencias con su código estable: avisos[i].texto es advertencias[i]. Un código desconocido vale como otro.
fuenteYesFuente para citar el dato.
origenYesapi: la API de MéxicoAPI; paquete: los datos y las reglas del paquete mexicoapi, sin red.
fuentesYesTodas las fuentes de la respuesta, empezando por fuente.
advertenciasYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/openWorld annotations it discloses the data source (MéxicoAPI public or MEXICOAPI_BASE), an automatic fallback to packaged data with a warning when the API fails, an offline switch via MEXICOAPI_SIN_RED=1, and that amounts are strings with two decimals. It also spells out the UMA validity window (1 Feb – 31 Jan), which is genuine behavioral context an agent could not infer.

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?

The description is front-loaded with the resource and then walks through the three modes in order, with no filler sentences. It is dense (one long chained sentence) but every clause carries routing or behavior information, so nothing needs cutting.

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?

For a read-only lookup tool with an output schema (so return shape needn't be described), the definition covers sources, fallback, offline mode, per-mode parameters, and value formatting. Nothing an agent needs to call it correctly is missing.

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 75%, and the description compensates well: it explains that fecha yields the UMA in force that day, that salario_minimo returns zona general plus Zona Libre de la Frontera Norte, and that periodo applies only to isr. The one gap is the unspecified default when tipo=uma is sent with neither anio nor fecha.

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 the concrete resource (UMA, salario mínimo and ISR rates published in the DOF) and the verb (retrieve/consult), and immediately enumerates the three modes via the tipo enum. An agent can tell this is a constants/lookup tool, distinct from sibling validators and calculators.

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?

It explicitly routes each mode: 'tipo uma con anio... o con fecha', 'tipo salario_minimo con anio', 'tipo isr con periodo... y anio', which tells the agent which parameter combination selects which behavior. It does not state when to prefer this over siblings or what happens if tipo=uma is sent with neither anio nor fecha, so it stops short of full when/when-not guidance.

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