Skip to main content
Glama

Banxico

by io.github.pipeworx-io
OverviewAdmin

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. Dates show when Glama detected each change.

  1. 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"
+  }
+]
  2. 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, etc. Description adds that it returns recent observations plus title/units, and its 'escape hatch' nature, providing useful behavioral context beyond annotations.

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 highly informative sentences with no wasted words. Purpose is front-loaded, followed by helpful examples and guidance.

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?

Given the rich annotations and sibling tool context, the description fully explains what the tool does, what it returns, and when to use it, making it complete for an agent.

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 already covers all parameters (100% coverage). Description adds value by listing common series IDs with their meanings, enhancing understanding beyond the schema descriptions.

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?

Clearly states it fetches any Banco de México SIE series by ID, listing specific categories (inflation, interest rates, etc.) and distinguishing it from sibling tools for specific series.

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?

Explicitly advises using banxico_exchange_rate or banxico_policy_rate for common headline series, and provides common IDs, guiding when to use this general tool.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources