Skip to main content
Glama

Inegi

by io.github.pipeworx-io

Inegi Indicator

inegi_indicator
Read-onlyIdempotent

Fetch any INEGI indicator by its numeric id, at a chosen geographic level — escape hatch for the full Banco de Indicadores (GDP, employment/ENOE, economic census, prices, etc.). Returns the latest value (or full history). Find indicator ids with INEGI's "Constructor de consultas" at inegi.org.mx/app/indicadores. NOTE: for Mexico inflation, interest rates, and the peso exchange rate, the banxico pack is usually the better source.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
areaNoGeographic area: "00" = national (default), "01"–"32" = state (e.g. "09" = Mexico City/CDMX, "07" = Chiapas, "15" = México state), or a 5-digit municipality code (state+municipio).
sourceNoData bank: "BISE" (Banco de Indicadores, default) or "BIE" (Banco de Información Económica — economic time series).
_apiKeyNoOptional — your own free INEGI API token. Omit to use the shared Pipeworx token.
all_historyNoReturn the full time series instead of just the latest observation. Default false.
indicator_idYesINEGI indicator id, e.g. "1002000001" (total population).

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-inegi-api-key",
+    "indicator_id": "1002000001"
+  },
+  {
+    "_apiKey": "your-inegi-api-key",
+    "all_history": true,
+    "area": "Jalisco",
+    "indicator_id": "1002000001"
+  }
+]
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations declare readOnlyHint, idempotentHint, and destructiveHint=false, which the description does not contradict. The description adds context about the shared API token and the ability to return full history, but no additional behavioral traits beyond what annotations already convey.

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 concise, front-loaded with the core purpose (fetch indicator), and includes only essential additional context such as the banxico note and ID discovery guidance. Every sentence contributes value.

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 simplicity (fetching indicators with rich schema), the description adequately covers the main functionality, return options (latest or full history), and important cross-references to alternative sources. Lack of output schema is offset by the straightforward nature of the operation.

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?

The input schema covers 100% of parameters with detailed descriptions, including area codes and source options. The description does not add new parameter semantics beyond the schema, but it reinforces the use case with an example ID and the note about the banxico alternative.

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?

The description clearly states the tool fetches INEGI indicators by numeric ID at a chosen geographic level, describes itself as an 'escape hatch' for the full Banco de Indicadores, and lists example domains (GDP, employment, etc.). This is a specific verb+resource scope that distinguishes it from sibling tools like inegi_population.

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?

The description explicitly advises against using this tool for Mexico inflation, interest rates, and exchange rates, directing the agent to the banxico pack instead. It also provides guidance on finding indicator IDs via INEGI's Constructor de consultas.

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

All Inegi 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