Skip to main content
Glama

BDRs

bdr
Read-onlyIdempotent

BDRs negociados na B3 (Apple AAPL34, Nvidia NVDC34, IVVB39): lista, preço em reais, rentabilidade e proventos. Use quando: "quais BDRs são mais negociados?"; "quanto rendeu AAPL34 em 5 anos?"; "BDR patrocinado ou não?". NÃO use para: ação brasileira → precos; ETF brasileiro → etf. Fonte e fórmula: cadastro e COTAHIST da B3; rentabilidade em reais, já com o câmbio; proventos por BDR em R$. Retorna: ticker="": lista {ticker, tipo, último fechamento, liquidez}; com ticker: cadastro, último pregão, rentabilidade com e sem proventos (1 mês a 10 anos), proventos e desdobramentos; serie=True: colunas/linhas. Vazio ou erro: não tem o código da ação lá fora nem a proporção BDR:ação. Série sem chave = amostra de 30 pregões. Acesso: Lista e AAPL34 abertos; detalhe dos demais exige chave_api (grátis).

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": "bdr"
  }
}

Input Schema

NameRequiredDescriptionDefault
deNoInício da série (com serie=True): AAAA-MM-DD (também aceita 2024, 2024-06, 06/2024 e 01/06/2024).
ateNoFim da série (com serie=True): AAAA-MM-DD (também aceita 2024, 2024-06, 06/2024 e 01/06/2024).
tipoNoFiltro de tipo de BDR: DRN, DR1, DR2, DR3 ou DRE. Vazio = todos.
serieNoFalse (padrão) = resumo; True = série diária em colunas. Sem chave_api a série vem como amostra dos últimos 30 pregões.
tickerNoTicker do BDR, como AAPL34, NVDC34 ou IVVB39. Vazio = lista os BDRs negociados no último ano.
chave_apiNoChave de API opcional. Vazia = acesso aberto: a descrição da ferramenta diz se devolve amostra ou exige chave (chave grátis, sem cartão).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / tipo / enum
      Added value: +[
      +  "",
      +  "DRN",
      +  "DR1",
      +  "DR2",
      +  "DR3",
      +  "DRE"
      +]
  2. Changed6 schema fields changed
    • addedInput schema / properties / ate / description
      Added value: +"Fim da série (com serie=True): AAAA-MM-DD (também aceita 2024, 2024-06, 06/2024 e 01/06/2024)."
    • addedInput schema / properties / chave_api / description
      Added value: +"Chave de API opcional. Vazia = acesso aberto: a descrição da ferramenta diz se devolve amostra ou exige chave (chave grátis, sem cartão)."
    • addedInput schema / properties / de / description
      Added value: +"Início da série (com serie=True): AAAA-MM-DD (também aceita 2024, 2024-06, 06/2024 e 01/06/2024)."
    • addedInput schema / properties / serie / description
      Added value: +"False (padrão) = resumo; True = série diária em colunas. Sem chave_api a série vem como amostra dos últimos 30 pregões."
    • addedInput schema / properties / ticker / description
      Added value: +"Ticker do BDR, como AAPL34, NVDC34 ou IVVB39. Vazio = lista os BDRs negociados no último ano."
    • addedInput schema / properties / tipo / description
      Added value: +"Filtro de tipo de BDR: DRN, DR1, DR2, DR3 ou DRE. Vazio = todos."
  3. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely non-annotated behavior: the data source (cadastro and COTAHIST from B3), that returns are in reais already currency-converted, and — most importantly — the access gating where list and AAPL34 are open while detail for other tickers requires a free `chave_api`. It does not mention rate limits or response latency, which keeps it from 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Heavily front-loaded with labelled sections (Use quando / NÃO use para / Fonte e fórmula / Retorna / Vazio ou erro / Acesso), which makes scanning easy. It is dense and slightly long, but almost every clause carries decision-relevant information; only the 'Fonte e fórmula' line is arguably optional for a caller.

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 must carry return-shape information, and it does so for all three modes (list, detail, series). It also covers edge cases an agent would otherwise stumble on: missing ticker or missing BDR:share ratio produces empty/error, and an unauthenticated series silently degrades to a 30-trading-day sample.

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%, so baseline is 3, but the description adds cross-parameter meaning the schema states only per-field: `ticker=""` yields a list of {ticker, tipo, último fechamento, liquidez}, a populated ticker yields cadastro plus rentabilidade horizons of 1 month to 10 years, and `serie=True` switches the payload to colunas/linhas. That interaction semantics is real added value beyond the enum and field descriptions.

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 resource (BDRs negociados na B3, with concrete examples AAPL34/NVDC34/IVVB39) and the four things it returns: list, price in reais, rentabilidade and proventos. It also names the two siblings it must not be confused with (`precos` for Brazilian stocks, `etf` for Brazilian ETFs), so an agent can route without opening any schema.

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?

The 'Use quando' block gives three literal example questions that map to distinct modes (ranking of most-traded, historical return, sponsored vs non-sponsored). The 'NÃO use para' block names the alternative tool for each excluded case, giving explicit when-not-to-use 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.