Skip to main content
Glama

Validar CLABE

validar_clabe
Read-onlyIdempotent

Validate an 18-digit Mexican CLABE by checking its control digit and bank code, then return the bank, branch, and account details without network calls or confirming the account exists.

Instructions

Valida una CLABE interbancaria de 18 dígitos: dígito de control y código de banco contra el catálogo de bancos que trae el paquete. Acepta espacios y guiones entre los dígitos. No usa la red ni confirma que la cuenta exista. Devuelve el banco (activo: false si ya no aparece en el SPEI), la plaza y la cuenta.

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": {
      "clabe": "<clabe>"
    },
    "name": "validar_clabe"
  }
}

Input Schema

NameRequiredDescriptionDefault
clabeYesLa CLABE, con o sin 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.7/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent and closed-world, and the description adds real context beyond them: no network call, no account-existence confirmation, tolerance for spaces and hyphens, and the semantics of the returned bank's activo flag when a bank has left SPEI. That is exactly the behavioral detail an agent cannot get from the structured fields.

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 short sentences, front-loaded with the core action, then constraints, then output shape. Every sentence carries distinct information with no repetition of the title or padding.

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 single-parameter validation tool with annotations and an output schema, nothing material is missing: input tolerance, offline nature, limitations, and the meaning of the returned activo flag are all stated. An agent can call it and interpret results without further inference.

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?

Only one parameter with 100% schema description coverage, so the baseline is 3. The description adds value by resolving the mismatch between the schema's maxLength 64 and the actual requirement of 18 digits, and by reiterating accepted separators — meaning beyond what the schema's types convey.

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?

States a specific verb and resource ("Valida una CLABE interbancaria de 18 dígitos") and narrows scope to two checks: control digit and bank code against the bundled catalog. The resource (CLABE) is inherently distinct from the sibling validators (CURP, RFC, NSS), so an agent can route correctly from the description alone.

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 bounds what the tool does not do: "No usa la red ni confirma que la cuenta exista", which tells the agent this is offline format/checksum validation rather than account verification. It gives clear context but does not name a sibling alternative for cases where a bank-code lookup (e.g. banco_por_codigo) might be the right call.

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