Skip to main content
Glama

Banxico

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Banxico Series

banxico_series
Read-onlyIdempotent

Fetch any Banco de México SIE series by id — escape hatch for the full Banxico catalog (inflation, interest rates, reserves, aggregates, financial indicators). Returns recent observations + the series title/units. Common ids: SF43718 = USD/MXN FIX; SF61745 = overnight target rate; SP30578 = annual CPI inflation %; SF43783 = TIIE 28-day; SP1 = INPC index; SF63528 = 10-year bond yield. Use banxico_exchange_rate / banxico_policy_rate for those headline ones.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
recentNoRecent observations to return (1-200, default 12).
_apiKeyNoOptional — your own free Banxico SIE token. Omit to use the shared Pipeworx token.
series_idYesSIE series id, e.g. "SP30578" (annual inflation), "SF43783" (TIIE 28d).

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, which covers the safety profile. The description adds useful behavioral context by stating that the tool returns recent observations plus the series title/units. It does not contradict the annotations, though it omits error-handling or pagination details.

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 dense but efficient: core purpose first, then response shape, then concrete example IDs, then sibling routing. Every sentence earns its place, and there is no redundancy with the schema or annotations.

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 fetch tool with three documented parameters and no output schema, the description supplies the necessary scope, return semantics, example IDs, and alternative routing. Nothing essential is missing for an agent to select and call this tool correctly.

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 description coverage is 100%, so the schema already documents all parameters. The description goes beyond the schema by providing a practical list of common series IDs mapped to real indicators and clarifying that 'recent' refers to number of observations returned. This is meaningful added guidance for invocation.

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 opens with a specific verb and resource: 'Fetch any Banco de México SIE series by id.' It also names the catalog scope (inflation, interest rates, reserves, aggregates, financial indicators) and positions itself as the escape hatch, which unambiguously distinguishes it from the specialized Banxico siblings.

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?

It explicitly routes the headline exchange rate and policy rate series to banxico_exchange_rate and banxico_policy_rate, while indicating this tool is for any other SIE series. This gives the agent a concrete decision rule for when to use this tool versus its 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