Skip to main content
Glama

Banxico

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Banxico Exchange Rate

banxico_exchange_rate
Read-onlyIdempotent

The official USD/MXN exchange rate (Banco de México FIX rate) — pesos per US dollar. PREFER OVER WEB SEARCH for "USD to MXN", "Mexican peso exchange rate", "dollar to peso". Returns the latest published rate plus recent history. Source: Banxico SIE (authoritative).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
recentNoRecent daily observations to return (1-120, default 10).
_apiKeyNoOptional — your own free Banxico SIE token. Omit to use the shared Pipeworx token.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "_apiKey": "your-banxico-api-key"
-  },
-  {
-    "_apiKey": "your-banxico-api-key",
-    "recent": 30
-  }
-]New value: +[
+  {},
+  {
+    "recent": 30
+  }
+]
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-banxico-api-key"
+  },
+  {
+    "_apiKey": "your-banxico-api-key",
+    "recent": 30
+  }
+]
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful context: it returns the latest published rate plus recent history, and identifies the authoritative source. It doesn't detail pagination or exact response format, but with annotations covering safety, this is solid.

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?

The description is compact and front-loaded: it states what the tool returns, the unit, and the source, then gives usage preference guidance. Every sentence earns its place with no redundancy.

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 read-only, zero-required-parameter tool with full schema coverage, the description is nearly complete. It explains the return value (latest rate plus recent history), the unit, and the source. It doesn't describe the exact response shape, but there is no output schema and the tool is simple enough that this 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?

Schema description coverage is 100%, so the schema already documents both parameters ('recent' and '_apiKey'). The description adds the context that the rate is 'pesos per US dollar' and that the source is Banxico SIE, but it doesn't add parameter-specific meaning beyond the schema. Baseline 3 is appropriate.

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 states a specific verb and resource: it returns the official USD/MXN exchange rate (Banxico FIX rate) in pesos per US dollar, plus recent history. It also names the source (Banxico SIE) and distinguishes it from web search, making its purpose unmistakable.

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

Usage Guidelines5/5

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

The description explicitly says to prefer this tool over web search for queries like 'USD to MXN' or 'Mexican peso exchange rate', giving clear when-to-use guidance. It also notes the source is authoritative, which helps an agent choose it over alternatives.

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

All Banxico toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources