Skip to main content
Glama

Latam Validate

Brasil Banks

brasil_banks
Read-onlyIdempotent

List Brazilian banks (COMPE code, ISPB, and name) from the central-bank registry, optionally filtered by name or code. Use to resolve a bank code from a boleto or PIX/TED transfer to the institution name, e.g. code 1 -> Banco do Brasil, 260 -> Nubank.

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": {
      "search": "nubank"
    },
    "name": "brasil_banks"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeNoExact COMPE bank code to look up, e.g. 341 for Itaú.
limitNoMax results when listing/filtering (default 25).
searchNoFilter by bank name substring (case-insensitive), e.g. "nubank" or "itau".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "search": "nubank"
      +  },
      +  {
      +    "code": 341
      +  }
      +]
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive behavior. The description adds that the source is the central-bank registry and discloses the returned fields (COMPE, ISPB, name), which matters since there is no output schema; it does not cover result ordering or pagination beyond the limit parameter.

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 the resource and its fields, then the use case. Every clause carries information; nothing is redundant with the name or title.

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 simple three-parameter lookup with no output schema, the description supplies the data source, the returned fields, and a realistic invocation scenario. Nothing an agent needs to call it correctly appears to be missing.

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%, so all three parameters are documented in the schema itself, setting the baseline at 3. The description reinforces that codes are COMPE codes with illustrative mappings, but adds no format or edge-case rules (e.g. zero-padding, partial code matching) beyond the schema.

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 and resource: 'List Brazilian banks (COMPE code, ISPB, and name) from the central-bank registry'. It also names the fields returned and the filtering options, so the agent knows exactly what it gets back and how it can be narrowed.

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 gives an explicit when-to-use case: resolving a bank code from a boleto or PIX/TED transfer to an institution name, reinforced with concrete mappings (1 -> Banco do Brasil, 260 -> Nubank). It does not name an alternative tool to prefer or an exclusion, but no obvious overlapping sibling exists in the catalog.

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.