Skip to main content
Glama

Banco por código

banco_por_codigo
Read-onlyIdempotent

Look up a Mexican bank or SPEI participant from the 3-digit CLABE prefix and get its short name, legal name, SPEI key, active status, and name history from an offline catalog.

Instructions

Devuelve un banco o participante del SPEI por el código de 3 dígitos con el que empieza la CLABE: nombre corto, razón social, clave SPEI, si sigue activo y su historial de nombres. Sale del catálogo que trae el paquete, sin red.

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": {
      "codigo": "<codigo>"
    },
    "name": "banco_por_codigo"
  }
}

Input Schema

NameRequiredDescriptionDefault
codigoYesLos 3 primeros dígitos de la CLABE.

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

A3.8/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety profile is covered. The description adds real context on top: the data comes from a bundled catalog and requires no network, and the response includes name history ('historial de nombres'), which hints at historical aliases. It does not say what happens with an unknown or inactive code, so it stops short of a 5.

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?

A single dense sentence, front-loaded with the verb and resource, followed by the returned fields and the offline constraint. No filler and nothing is buried.

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 one-parameter lookup with high schema coverage, an output schema, and clear annotations, the description covers purpose, data source, and field list. The only gap is edge-case behavior (unknown or retired code, case of an inactive bank), which a caller might reasonably want stated.

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?

There is a single parameter with a 3-digit pattern and the schema description ('Los 3 primeros dígitos de la CLABE') already covers the same ground as the description's mention of the CLABE prefix. With full schema coverage, the description adds no meaning beyond the input schema, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete verb and resource ('Devuelve un banco o participante del SPEI') and pins the exact lookup key (the 3-digit CLABE prefix), so an agent knows precisely what this returns. It does not name or contrast with a sibling such as validar_clabe, which is why it falls short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The use case is implied by 'por el código de 3 dígitos con el que empieza la CLABE' and 'sin red', but the description never states when to prefer this over the catalog/validation siblings. No exclusion or alternate path is offered.

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