Banxico (Banco de México)

consultar_serie_sie

Consulta avanzada para obtener observaciones de cualquier serie económica del catálogo SIE de Banxico.

Args: id_serie: Identificador de la serie oficial (por ejemplo: 'SF43718', 'SP68257', 'SF61745'). fecha_inicio: Fecha inicial en formato YYYY-MM-DD o DD/MM/YYYY (opcional). fecha_fin: Fecha final en formato YYYY-MM-DD o DD/MM/YYYY (opcional).

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": {
      "id_serie": "<id_serie>"
    },
    "name": "consultar_serie_sie"
  }
}

Input Schema

Name	Required	Description	Default
`id_serie`	Yes
`fecha_fin`	No
`fecha_inicio`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 28, 2026

TDQS

A4.1/5.0

Behavior3/5

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

With no annotations, the description carries the behavioral disclosure burden. It communicates a read-only query ('Consulta') that returns observations, but it does not mention rate limits, authorization needs, error behavior, or what happens when date filters are omitted. This is adequate for a simple query tool but not deeply transparent.

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?

Opens with a one-sentence purpose statement followed by a compact Args list that maps directly to the schema. There is no filler, and every line contributes useful information.

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?

The output schema covers return structure, and the description fully documents the parameters and the generic scope, making invocation clear. It lacks explicit sibling routing and behavioral caveats, but these are minor given the simple read-only nature of the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description fully compensates. It explains id_serie with concrete examples and specifies accepted date formats for both optional parameters, adding essential meaning beyond the bare schema properties.

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?

States a specific verb and resource: 'obtener observaciones de cualquier serie económica del catálogo SIE de Banxico'. The phrase 'cualquier serie' clearly distinguishes it from sibling tools like tipo_cambio_usd or inflacion_mexico, which are specific-series helpers.

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

Usage Guidelines3/5

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

Usage is implied through 'cualquier serie económica': an agent can infer this is the generic tool for arbitrary SIE series while siblings cover specific ones. However, it never explicitly states when to prefer this tool over the alternatives or when not to use it.

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

All Banxico (Banco de México) tools Inspect

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.