Skip to main content
Glama
cfocoder

Banxico MCP Server

get_unemployment_data

Retrieve current and historical unemployment rate data from Mexico's central bank (Banxico) for economic analysis and monitoring.

Instructions

Get unemployment rate data from Banxico.

Args: limit: Maximum number of recent data points (default: 24 for 2 years of monthly data)

Returns: Current and historical unemployment rate data

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function decorated with @mcp.tool(), which registers the tool and implements the core logic: fetches unemployment data (series SL1) from Banxico API, handles token check and errors, applies data limit, and returns formatted output.
    @mcp.tool()
    async def get_unemployment_data(limit: Optional[int] = 24) -> str:
        """
        Get unemployment rate data from Banxico.
        
        Args:
            limit: Maximum number of recent data points (default: 24 for 2 years of monthly data)
            
        Returns:
            Current and historical unemployment rate data
        """
        if not BANXICO_TOKEN:
            return "Error: BANXICO_API_TOKEN environment variable not set. Please configure your API token."
        
        endpoint = "series/SL1/datos"
        data = await make_banxico_request(endpoint, BANXICO_TOKEN)
        
        if not data:
            return "Failed to retrieve unemployment 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_unemployment_data(data)
  • Supporting function that formats the raw unemployment data from Banxico API into a human-readable string, including emojis, units, recent data points with percentage formatting, and structured output.
    def format_unemployment_data(data: dict[str, Any]) -> str:
        """
        Format unemployment data with percentage symbols and labor market formatting.
        
        Args:
            data: Raw JSON response from Banxico API
            
        Returns:
            Formatted string with unemployment rate data
        """
        if not data or "bmx" not in data:
            return "No unemployment data available"
        
        series_list = data["bmx"].get("series", [])
        if not series_list:
            return "No unemployment 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 percentage formatting
                display_count = min(len(datos), 12)  # Show more for unemployment trends
                for dato in datos[-display_count:]:
                    fecha = dato.get("fecha", "Unknown date")
                    valor = dato.get("dato", "N/A")
                    # Add percentage symbol for unemployment rate
                    if valor != "N/A" and valor is not None:
                        try:
                            valor_num = float(valor)
                            valor = f"{valor_num}%"
                        except (ValueError, TypeError):
                            pass
                    result.append(f"  {fecha}: {valor}")
            
            result.append("")  # Empty line between series
        
        return "\n".join(result)
  • General utility function used by the tool (and others) to perform asynchronous HTTP requests to the Banxico API, handling authentication, errors, and returning parsed JSON 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
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 mentions the tool returns 'Current and historical unemployment rate data,' which implies a read-only operation, but doesn't cover critical aspects like rate limits, authentication needs, data freshness, or error handling. For a data-fetching tool with zero annotation coverage, this is insufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured and front-loaded with the core purpose, followed by clear sections for Args and Returns. It's concise with no wasted sentences, though the 'Returns' section is somewhat redundant given the output schema, slightly reducing efficiency.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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) and the presence of an output schema, the description is minimally adequate. It covers the purpose and parameter semantics but lacks behavioral details and usage guidelines. Without annotations, it should do more to explain data scope or limitations, making it just sufficient but not comprehensive.

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 its default value (24) and purpose ('2 years of monthly data'), which goes beyond the input schema's basic type and default. With 0% schema description coverage, this compensation is effective, though it could detail format or constraints more.

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 unemployment rate data from Banxico.' It specifies the verb ('Get'), resource ('unemployment rate data'), and source ('Banxico'). However, it doesn't explicitly differentiate from sibling tools like 'get_inflation_data' or 'get_usd_mxn_historical_data' beyond the data type, which keeps it from 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 or contexts where other tools might be more appropriate, such as using 'get_inflation_data' for inflation metrics or 'get_date_range_data' for broader queries. This leaves the agent without clear usage instructions.

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