Skip to main content
Glama

Latam Validate

Validate Clabe

validate_clabe
Read-onlyIdempotent

Validate a Mexican CLABE (Clave Bancaria Estandarizada, the 18-digit interbank account number used for SPEI transfers). Checks the control-digit checksum and decodes the bank code, plaza (branch city) code, and account number. Resolves the bank name for major Mexican banks (BBVA, Banorte, Santander, Banamex, Banco Azteca, STP, Nu, Mercado Pago, ...). Pure computation, accepts spaces or dashes in the input.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

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

Input Schema

NameRequiredDescriptionDefault
clabeYesThe 18-digit CLABE, e.g. "002010077777777771". Spaces and dashes are allowed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "clabe": "002010077777777771"
      +  },
      +  {
      +    "clabe": "002 0100 7777 7777 71"
      +  }
      +]
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent and non-destructive semantics, and the description adds genuinely new behavioral context: it is pure computation (no network or state), it tolerates spaces or dashes in input, and it reports bank name only for major banks rather than all institutions. The one meaningful omission is what happens on an invalid checksum — whether it errors or returns a negative result — which matters for agent control flow.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the verb and resource in the first clause, then progressive detail; every sentence carries information and the parenthetical expansion and bank list are genuinely useful rather than filler. The '(BBVA, Banorte, ... , ...)' enumeration is slightly bulky but signals partial coverage, which is worth the words.

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 single-parameter pure-computation tool with no output schema, the description adequately conveys what comes back (validity plus decoded bank code, plaza, account number, resolved bank name), which is what an agent needs to plan on the result. The remaining gap, the shape of a failed validation, is the only thing an agent could still trip on.

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 already documents the 18-digit format with examples and the spaces/dashes tolerance, so the description only restates 'accepts spaces or dashes in the input' without adding syntax or validation rules beyond the schema. Baseline 3 applies when the schema does the heavy lifting; the '18-digit' framing in the description is a minor reinforcement rather than new meaning.

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?

Specific verb plus resource ('Validate a Mexican CLABE') with the acronym spelled out and the domain use case (interbank account number for SPEI transfers) explained, so an agent unfamiliar with Mexican banking identifiers can still act. It also enumerates the internal checks (control-digit checksum, bank/plaza/account decoding, bank-name resolution) that define what the tool actually does, distinguishing it immediately from the Brazilian document validators in the sibling list.

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 context is clear: this is the tool for Mexican CLABE validation before initiating or reconciling SPEI transfers, and 'Pure computation' signals it is a safe local check rather than a lookup. It stops short of explicit routing language (no 'use validate_cpf/validate_cnpj for Brazilian documents' pointer), but the currency/identifier specificity makes misselection unlikely.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.