Skip to main content
Glama

Validar CURP

validar_curp
Read-onlyIdempotent

Validate a Mexican CURP’s 18-character format—birth date, sex, state code, and check digit—locally without network access or RENAPO existence checks.

Instructions

Valida el formato de una CURP: estructura, fecha de nacimiento, sexo, entidad y dígito verificador. Corre en el equipo, sin red; no consulta a RENAPO ni confirma que la CURP exista.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "curp": "<curp>"
    },
    "name": "validar_curp"
  }
}

Input Schema

NameRequiredDescriptionDefault
curpYesLa CURP de 18 caracteres; se ignoran mayúsculas, espacios y guiones.

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.2/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 the safety profile is covered. The description adds valuable context beyond that: it runs locally without network, does not consult RENAPO, and does not confirm the CURP exists. It does not cover return values or error handling, which is acceptable since an output schema exists.

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 what is validated, followed by practical limitations. Every sentence earns its place with no redundant or vague wording.

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?

For a simple validator with one well-documented parameter and an output schema, the description is nearly complete: it covers scope, offline behavior, and what is not checked. The only minor gap is that it does not mention what kind of result is returned, but the output schema fills that role.

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?

Schema coverage is 100%, and the single parameter is fully described in the schema (18 characters, case/space/hyphen insensitive). The description adds no additional meaning about the parameter beyond what the schema already provides, so 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 uses a specific verb 'Valida' with the resource 'CURP' and enumerates exactly what is checked: structure, birth date, sex, entity, and check digit. This clearly distinguishes it from sibling validators like validar_rfc or validar_nss without needing to name them.

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?

The description provides clear context for when to use it by stating it validates CURP format and explicitly notes it does not query RENAPO or confirm existence, implying it should not be used for existence verification. However, it does not explicitly name alternative tools or state when to prefer them, keeping it from a 5.

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