Skip to main content
Glama

get_bank

Retrieve details of a Brazilian bank using its COMPE code, such as 260 for Nubank. Use bank codes to identify official bank information via the Brazil Data MCP server.

Instructions

Return details of a Brazilian bank by its COMPE code (e.g. 260 for Nubank).

Args: code: Bank code.

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": {
      "code": "<code>"
    },
    "name": "get_bank"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden; 'Return' correctly implies a read-only operation and the example clarifies the code format. However, it never says what 'details' actually contains, nor how it behaves when the code is not found, leaving the return side of the behavior undefined.

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?

One front-loaded sentence carries the core meaning, followed by a short Args block. The trailing 'code: Bank code.' largely repeats the schema title and adds little, but overall there is no padding or wasted prose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 no output schema and no annotations, the essentials (what the tool is, what the key is, an example) are present. Missing are the shape of the returned bank record and error/not-found behavior, which matter because no output schema exists to fill that gap.

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 0% and the schema only says 'Code' as an integer, so the description does real work by naming COMPE as the code system and supplying a worked example (260 → Nubank). It does not state the valid numeric range or whether leading zeros matter, so it is strong but not complete.

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 states a specific verb and resource — 'Return details of a Brazilian bank by its COMPE code' — and anchors the identifier space with a concrete example (260 for Nubank). It is unambiguously distinct from the sibling tools (address, IPCA, PTAX, SELIC, holidays), though it never explicitly names an alternative, so it falls just 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?

Usage is only implied: it is clearly a single-record lookup keyed by a bank code, but the description gives no explicit when-to-use, no prerequisites, and no guidance on what to do for an invalid or unknown code. For a single-purpose lookup this is adequate but unelaborated.

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