Skip to main content
Glama

Estados

estados
Read-onlyIdempotent

Retrieves the 32 INEGI federal entities with their 2-digit state key, name, abbreviation, and cvegeo, so you can obtain the state key required by municipality lookup tools.

Instructions

Las 32 entidades federativas del catálogo de INEGI que trae el paquete, sin red: clave de 2 dígitos (cve_ent), nombre, abreviatura y cvegeo. Úsala para saber la clave de un estado, que piden municipios_de_estado y buscar_municipio.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "estados"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
as_ofYesFecha de corte del dataset: la de la última actualización que lo cambió (en los datos curados, la publicación más reciente de sus fuentes). No es la fecha del valor, que va en datos.
datosYes
avisosYesLas advertencias con su código estable: avisos[i].texto es advertencias[i]. Un código desconocido vale como otro.
fuenteYesFuente para citar el dato.
origenYespaquete: los datos y las reglas del paquete mexicoapi, sin red.
fuentesYesTodas las fuentes de la respuesta, empezando por fuente.
advertenciasYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint=false and idempotentHint, so safety is covered. The description adds genuine context beyond them: the data comes from a bundled INEGI catalog ('sin red'), it is exhaustive at 32 entities, and each record carries four specific attributes. It does not describe result ordering or cardinality beyond the count, but with annotations and an output schema present, that is a minor gap.

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: the first front-loads what the tool returns and its offline nature, the second gives the use case. Nothing is repeated from annotations and no wording is wasted.

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?

For a zero-parameter, read-only catalog tool with rich annotations and an existing output schema, the description supplies everything an agent needs: source, scope, completeness, offline behavior, returned attributes, and the downstream call it unblocks. No further detail would be actionable.

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 tool takes zero parameters, so the baseline is 4. The description correctly spends no space on inputs and instead uses the room to characterize the returned fields, which is the right allocation for a parameterless tool.

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 names the concrete resource ('Las 32 entidades federativas del catálogo de INEGI') and its fixed scope (32 items, bundled with the package, no network), and lists the exact fields returned (cve_ent, nombre, abreviatura, cvegeo). An agent immediately knows this is a static catalog lookup, not a search or a network call.

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 states the purpose explicitly ('Úsala para saber la clave de un estado') and names the downstream consumers that require that key ('que piden municipios_de_estado y buscar_municipio'), which effectively routes the agent between this tool and the two siblings. The condition that selects this tool is unambiguous.

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