Skip to main content
Glama
cfocoder

Banxico MCP Server

get_banxico_reserves_data

Retrieve current and historical reserve assets data from Mexico's central bank (Banxico) for financial analysis and monitoring.

Instructions

Get Banxico Reserve Assets data.

Args: limit: Maximum number of recent data points (default: 30)

Returns: Current and historical Banxico reserve assets data

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Handler function for get_banxico_reserves_data tool. Fetches reserve assets data (series SF308843) from Banxico API, applies optional limit to recent data points, and formats the output using format_financial_data.
    @mcp.tool()
    async def get_banxico_reserves_data(limit: Optional[int] = 30) -> str:
        """
        Get Banxico Reserve Assets data.
        
        Args:
            limit: Maximum number of recent data points (default: 30)
            
        Returns:
            Current and historical Banxico reserve assets data
        """
        if not BANXICO_TOKEN:
            return "Error: BANXICO_API_TOKEN environment variable not set. Please configure your API token."
        
        endpoint = "series/SF308843/datos"
        data = await make_banxico_request(endpoint, BANXICO_TOKEN)
        
        if not data:
            return "Failed to retrieve Banxico reserve assets data. Please check your API token and network connection."
        
        # Apply limit if specified
        if limit and data.get("bmx", {}).get("series"):
            for series in data["bmx"]["series"]:
                if "datos" in series and len(series["datos"]) > limit:
                    series["datos"] = series["datos"][-limit:]
        
        return format_financial_data(data)
  • Helper function to make authenticated HTTP requests to the Banxico SIE API, used by get_banxico_reserves_data.
    async def make_banxico_request(endpoint: str, token: str) -> dict[str, Any] | None:
        """
        Make a request to the Banxico SIE API with proper error handling.
        
        Args:
            endpoint: The API endpoint to call (without base URL)
            token: The Banxico API token
            
        Returns:
            JSON response data or None if request failed
        """
        url = f"{BANXICO_API_BASE}/{endpoint}"
        headers = {"User-Agent": USER_AGENT}
        params = {"token": token}
        
        try:
            async with httpx.AsyncClient() as client:
                response = await client.get(url, headers=headers, params=params, timeout=30.0)
                response.raise_for_status()
                return response.json()
        except httpx.HTTPError as e:
            logger.error(f"HTTP error occurred: {e}")
            return None
        except Exception as e:
            logger.error(f"An error occurred: {e}")
            return None
  • Helper function to format financial data (used for reserves), including units, recent data points with comma-formatted large numbers.
    def format_financial_data(data: dict[str, Any]) -> str:
        """
        Format financial data with appropriate units and formatting.
        
        Args:
            data: Raw JSON response from Banxico API
            
        Returns:
            Formatted string with financial data
        """
        if not data or "bmx" not in data:
            return "No financial data available"
        
        series_list = data["bmx"].get("series", [])
        if not series_list:
            return "No financial series found"
        
        result = []
        for series in series_list:
            title = series.get("titulo", "Unknown Series")
            series_id = series.get("idSerie", "Unknown ID")
            unit = series.get("unidad", "")
            result.append(f"💰 {title} (ID: {series_id})")
            if unit:
                result.append(f"  Unit: {unit}")
            
            datos = series.get("datos", [])
            if not datos:
                result.append("  No data points available")
            else:
                result.append(f"  Total data points: {len(datos)}")
                # Show recent data points with number formatting
                display_count = min(len(datos), 10)
                for dato in datos[-display_count:]:
                    fecha = dato.get("fecha", "Unknown date")
                    valor = dato.get("dato", "N/A")
                    # Format large numbers with commas
                    if valor != "N/A" and valor is not None:
                        try:
                            valor_num = float(valor)
                            if valor_num >= 1000:
                                valor = f"{valor_num:,.2f}"
                            else:
                                valor = f"{valor_num}"
                        except (ValueError, TypeError):
                            pass
                    result.append(f"  {fecha}: {valor}")
            
            result.append("")  # Empty line between series
        
        return "\n".join(result)
  • FastMCP decorator that registers the get_banxico_reserves_data function as a tool.
    @mcp.tool()
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool 'Get[s]' data, implying a read-only operation, but doesn't clarify aspects like authentication needs, rate limits, data freshness, or error handling. For a data-fetching tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 well-structured and concise, using clear sections ('Args:', 'Returns:') without unnecessary details. Every sentence adds value: the first states the purpose, and the subsequent lines explain parameters and returns efficiently. It's front-loaded with the core functionality, making it easy to scan and understand.

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?

Given the tool's low complexity (1 parameter, no nested objects) and the presence of an output schema (which handles return value documentation), the description is reasonably complete. It covers the purpose, parameter semantics, and return scope. However, the lack of usage guidelines and behavioral details (e.g., data source or update frequency) prevents a perfect score, as these could aid the agent in contextual decisions.

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?

The description adds meaningful context for the single parameter 'limit' by explaining it as 'Maximum number of recent data points (default: 30).' This clarifies its purpose beyond the schema's technical definition. With 0% schema description coverage, the description fully compensates, providing essential semantic information that aids correct usage.

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 clearly states the tool's purpose: 'Get Banxico Reserve Assets data.' This specifies the verb ('Get') and resource ('Banxico Reserve Assets data'), making it immediately understandable. However, it doesn't differentiate this tool from its siblings (like get_cetes_28_data or get_inflation_data) beyond the specific data type, which prevents a perfect score.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools, context for selecting reserve assets data over other economic indicators, or any prerequisites. The agent must infer usage from the tool name alone, which is insufficient for effective decision-making.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/cfocoder/banxico_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server