Skip to main content
Glama

Inegi

by io.github.pipeworx-io

Inegi Population

inegi_population
Read-onlyIdempotent

Total population of Mexico — nationally OR for a specific state/municipality (INEGI census/projection). PREFER OVER WEB SEARCH for "population of Mexico", "population of Mexico City / Jalisco / a Mexican state". INEGI's strength is the geographic detail. Returns the value with its reference year.

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).
_apiKeyNoOptional — your own free INEGI API token. Omit to use the shared Pipeworx token.

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",
+    "area": "Mexico"
+  },
+  {
+    "_apiKey": "your-inegi-api-key",
+    "area": "Mexico City"
+  }
+]
  2. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already provide readOnlyHint, openWorldHint, idempotentHint, destructiveHint. Description adds 'Returns the value with its reference year', but little beyond that.

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?

Two sentences, front-loaded with purpose. Every sentence adds value, no redundancy.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite no output schema, it mentions return value and reference year. Covers purpose, granularity, and usage preference. Adequate for a simple tool with good annotations.

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?

100% schema coverage, so baseline 3. Description does not add extra meaning beyond the schema's parameter descriptions.

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?

Clearly states it retrieves total population of Mexico at national, state, or municipality level. Distinguishes from sibling tools like inegi_indicator.

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

Usage Guidelines4/5

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

Explicitly advises preference over web search for population queries, and highlights INEGI's geographic detail. Does not explicitly state when not to use, but context is clear.

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