Skip to main content
Glama

Validate Mexican CLABE (SPEI)

mx_clabe
Read-onlyIdempotent

Validate an 18-digit Mexican CLABE bank account: SPEI bank code (with bank name), plaza, account and check digit. Offline; does not confirm the account exists. Price: 0.01 USDC per successful call on Base via x402 (pass the signed payment in _meta['x402/payment']; failed calls are not charged). HTTP equivalent: POST https://json-canon-x402.fly.dev/v1/mx/clabe.

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": {
      "value": "<value>"
    },
    "name": "mx_clabe"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYesCLABE (18 digits). Spaces, dashes and lowercase are normalized.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent and closed-world, and the description adds material context beyond them: the validation is offline, existence of the account is not verified, and there is a metered cost model (0.01 USDC per successful call, charged via x402 payment passed in _meta, failures not charged). That payment mechanic is essential operational knowledge an agent cannot get from annotations or schema.

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 sentences, front-loaded with purpose, then the caveat, then cost and transport. Every clause carries operational weight (offline limitation, pricing, payment field, HTTP fallback) with no filler.

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?

There is no output schema, and the description implies the response reports the parsed components (bank name, plaza, check digit) but never states the actual return shape or a valid/invalid flag. For a single-parameter validator with read-only annotations this is close to complete, with the return-format gap being the only notable omission.

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?

Schema coverage is 100% and there is only one parameter, so the schema already carries the baseline. The description still adds meaning by stating the 18-digit length and enumerating the structural components being checked, which helps an agent understand what a valid value looks like beyond the example string.

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 opens with a specific verb and resource ('Validate an 18-digit Mexican CLABE bank account') and decomposes the target into bank code, plaza, account and check digit. An agent can distinguish this from sibling validators like mx_curp and mx_rfc purely from the text, since the resource and standard (SPEI) are named.

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?

It gives a clear scope boundary: the check is offline and 'does not confirm the account exists', which tells the agent when the result is sufficient and when it is not. It does not name alternative tools for the cases this one cannot cover, so it stops short of full when/when-not routing.

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.

Resources