Skip to main content
Glama

Inegi

by io.github.pipeworx-io
OverviewDiscussionsAdmin

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.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "_apiKey": "your-inegi-api-key",
-    "indicator_id": "1002000001"
-  },
-  {
-    "_apiKey": "your-inegi-api-key",
-    "all_history": true,
-    "area": "Jalisco",
-    "indicator_id": "1002000001"
-  }
-]New value: +[
+  {
+    "indicator_id": "1002000001"
+  },
+  {
+    "all_history": true,
+    "area": "Jalisco",
+    "indicator_id": "1002000001"
+  }
+]
  2. 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"
+  }
+]
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The description adds behavioral detail beyond the annotations by stating it 'Returns the latest value (or full history)' and mentions geographic level filtering. The annotations already declare readOnly, idempotent, and non-destructive, so the description need not repeat those. It does not mention rate limits or auth, but the shared-token note is covered in the schema and the behavior is well-scoped for a read-only fetch.

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?

Three sentences plus a note, each earning its place. The core action and scope are front-loaded, the return behavior follows, and the external lookup hint and banxico alternative are appended without bloat. No repetition of schema content or filler.

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 description covers the key operational concerns: what data it fetches, how to specify geography, what the output granularity is (latest vs. full history), and where to find IDs. Given the simple read-only nature and the absence of an output schema, it is adequately complete for an agent to call it correctly. It could mention expected response format, but that is not critical for a generic fetch tool.

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 has 100% coverage and describes every parameter with examples (e.g., indicator_id '1002000001', area codes). The description adds broader context by naming the data domains (GDP, employment/ENOE, etc.) and pointing to the ID look-up tool, which helps with parameter selection. However, this is marginal on top of an already complete schema, so the baseline 3 is appropriate.

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 opens with 'Fetch any INEGI indicator by its numeric id, at a chosen geographic level', which is a specific verb-resource pair and immediately distinguishes it as a general-purpose data retrieval tool. Calling it an 'escape hatch for the full Banco de Indicadores' further clarifies its scope and differentiates it from more specialized siblings 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?

It explicitly tells users when not to use this tool: 'for Mexico inflation, interest rates, and the peso exchange rate, the banxico pack is usually the better source.' It also points to INEGI's 'Constructor de consultas' for finding indicator IDs, which is a practical prerequisite. This is clear, specific guidance that helps an agent decide between this and alternatives.

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