Banxico SIE MCP Server

Overview Schema Source Related Servers Discussions Admin

convertir_mxn_divisa

Convert Mexican pesos to USD, EUR, JPY, GBP, or CAD using the exact exchange rate for a chosen date. Provide amount, currency, and date to get the foreign-currency value.

Instructions

Convierte pesos a divisa (USD/EUR/JPY/GBP/CAD) a fecha exacta. / MXN to FX.

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": {
      "monto_mxn": "<monto_mxn>",
      "divisa": "<divisa>",
      "fecha": "<fecha>"
    },
    "name": "convertir_mxn_divisa"
  }
}

Input Schema

Name	Required	Description	Default
`fecha`	Yes
`divisa`	Yes
`monto_mxn`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 17, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations, the description carries the full behavioral burden, yet it discloses only the supported currencies and that the rate is for an exact date. It says nothing about rate source, supported date ranges, permissions, error behavior for invalid dates/currencies, or the return structure.

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 bilingual sentences with the core purpose front-loaded and zero filler. Every fragment earns its place, making it easy for an agent to parse quickly.

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 3-parameter conversion tool with no annotations and no output schema, the description covers the purpose and currency domain but leaves significant gaps: expected fecha format and what the tool returns. The agent can call it, but with avoidable uncertainty.

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 coverage is 0%, so the description must compensate. It does add meaning by listing the allowed divisa values (USD/EUR/JPY/GBP/CAD) and implying fecha is a specific date, but it omits date format and any constraints on monto_mxn, leaving key parameter semantics incomplete.

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 states a specific verb and resource: 'Convierte pesos a divisa' with an explicit list of target currencies and the 'a fecha exacta' scope. It clearly distinguishes a MXN-to-FX conversion from siblings like convertir_udis_a_pesos, though it does not name any alternative tool.

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, no exclusions, and no pointer to alternatives such as get_tasa_hoy or get_divisas_rango. The agent can only infer that this is the conversion tool from the name and description; no conditions or prerequisites are stated.

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

Deploy Server