Skip to main content
Glama
Sign In

Dados B3

by io.github.Val7h
OverviewDiscussionsAdmin

Indicadores dos bancos listados (Banco Central)

bancos
Read-onlyIdempotent

Basileia, inadimplência acima de 90 dias, carteira de crédito e lucro dos BANCOS listados, por trimestre. Use quando: "qual banco tem a maior inadimplência?"; "índice de Basileia do Itaú"; "compare BBAS3 e BBDC4". NÃO use para: ROE anual do banco → indicadores_anuais; P/L ou P/VP do banco → multiplos; dividendos do banco → dividendos. Fonte e fórmula: IF.data do Banco Central (conglomerado prudencial, ODbL), sem recálculo; inadimplência = divisão de duas linhas do próprio BC. Retorna: sem ticker: bancos (último trimestre de cada um em ultimo, ordem da carteira de crédito); com ticker: serie trimestral {basileia_pct, inadimplencia_90d_pct, carteira_credito_rs_mil}. Vazio ou erro: ticker que não é banco devolve erro: chame sem ticker para ver os bancos cobertos. Acesso: Gratuita, sem chave.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
tickerNoTicker de banco opcional, como ITUB4, BBDC4, BBAS3 ou SANB11. Vazio = todos os bancos, último trimestre.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / ticker / description
      Added value: +"Ticker de banco opcional, como ITUB4, BBDC4, BBAS3 ou SANB11. Vazio = todos os bancos, último trimestre."
  2. Added

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond the annotations (which only declare read-only, idempotent, no destruction, closed-world) by disclosing the data source (IF.data do Banco Central, conglomerado prudencial, ODbL), that values are not recalculated, and how inadimplência is derived. It also documents error behavior for a non-bank ticker and confirms free access with no key, which the annotations do not convey.

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?

Front-loaded with the resource, then cleanly segmented by explicit labels (Use quando / NÃO use para / Fonte e fórmula / Retorna / Vazio ou erro / Acesso). Density is high but no sentence is filler; the ordering of return shapes before error handling matches how a caller reads it.

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?

With no output schema, the description carries the return contract itself and does so by naming both response shapes and the three serie fields. Combined with source provenance, error handling, and access terms, an agent has everything needed to call it and interpret the result correctly.

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 already explains the ticker parameter, but the description adds the crucial branch semantics: empty ticker returns one row per bank in `ultimo`, ordered by carteira de crédito, while a ticker returns the quarterly `serie` with three named fields. It also warns that a non-bank ticker raises an error, implying the caller should omit the parameter to discover coverage.

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?

States a specific set of resources (Basileia, inadimplência 90d, carteira de crédito, lucro) for a specific entity class (BANCOS listados) at a specific frequency (por trimestre). The uppercase 'BANCOS listados' plus the 'Basileia/inadimplência' field list makes it unmistakable versus fatos_contabeis or indicadores_anuais.

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

Usage Guidelines5/5

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

Provides explicit trigger phrases ('qual banco tem a maior inadimplência?', 'índice de Basileia do Itaú', 'compare BBAS3 e BBDC4') and an explicit NÃO use block that routes three out-of-scope intents to the correct siblings (indicadores_anuais for annual ROE, multiplos for P/L and P/VP, dividendos for dividends). When-to-use and when-not-to-use are both covered with named alternatives.

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

All Dados B3 toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources