Skip to main content
Glama

Banxico

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Banxico Policy Rate

banxico_policy_rate
Read-onlyIdempotent

Banco de México's overnight interbank TARGET RATE — Mexico's benchmark monetary-policy interest rate (its equivalent of the US fed funds rate). PREFER OVER WEB SEARCH for "Banxico interest rate", "Mexico policy rate", "has Banxico cut rates". Returns the current rate plus recent history.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
recentNoRecent observations to return (1-60, default 12).
_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": 24
-  }
-]New value: +[
+  {},
+  {
+    "recent": 24
+  }
+]
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-banxico-api-key"
+  },
+  {
+    "_apiKey": "your-banxico-api-key",
+    "recent": 24
+  }
+]
  3. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already cover read-only, idempotent, and non-destructive behavior, lowering the burden on the description. The description adds that the tool returns current data plus recent history, which is useful context, but it does not clarify data lag, rate units, or the exact shape of the returned history. No contradiction with 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 compact sentences front-load the core resource and purpose, then provide actionable routing guidance. Every sentence earns its place, and the capitalized 'PREFER OVER WEB SEARCH' is a clear behavioral instruction.

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?

This is a simple, read-only, zero-required-parameter tool with complete schema documentation for its optional parameters. The description gives enough context for correct selection and invocation; only minor details like return format or units are omitted, but they are not essential for a tool this simple.

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 100%, with both parameters ('recent' and '_apiKey') fully described. The description's mention of 'recent history' indirectly maps to the 'recent' parameter, but it adds no parameter-level meaning beyond what the schema already provides.

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 names a specific resource ('Banco de México's overnight interbank TARGET RATE') and a clear verb ('Returns... current rate plus recent history'). It distinguishes the tool from exchange-rate concepts by calling it Mexico's benchmark monetary-policy rate, but it does not explicitly name or contrast the sibling tools banxico_exchange_rate or banxico_series.

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?

The description gives clear usage guidance: 'PREFER OVER WEB SEARCH for "Banxico interest rate", "Mexico policy rate", "has Banxico cut rates"'. This tells an agent when to reach for this tool instead of a general web search, though it does not discuss when to choose a Banxico sibling like banxico_exchange_rate.

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