Skip to main content
Glama
Sign In

Dados B3

by io.github.Val7h
OverviewDiscussionsAdmin

Quanto rendeu R$ 1.000 em 1, 3, 5 e 10 anos

quanto_rendeu
Read-onlyIdempotent

Quanto viraram R$ 1.000 numa ação, FII ou ETF em 1, 3, 5 e 10 anos, com e sem dividendos reinvestidos. Use quando: "quanto rendeu R$ 1.000 em ITUB4 nos últimos 5 anos?"; "o HGLG11 rendeu mais que o IFIX?"; "BOVA11 em 10 anos contra a Selic". NÃO use para: período escolhido (de/até) de uma ação → desempenho; só os dividendos → dividendos. Fonte e fórmula: COTAHIST da B3 e proventos registrados; janelas terminam no último fechamento; comparação com IBOV (IFIX para FII) e meta Selic; sem custos nem impostos. Mesmos números de /quanto-rendeu/TICKER. Retorna: texto em markdown com o valor final por janela, url e citacao. Vazio ou erro: janela sem histórico fica de fora do texto. Código desconhecido devolve erro; código antigo segue a troca sozinho. Acesso: Aberta, sem chave, qualquer ticker de ação, FII ou ETF.

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": {
      "ticker": "<ticker>"
    },
    "name": "quanto_rendeu"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYesTicker de ação, FII ou ETF da B3, como PETR4, HGLG11 ou BOVA11 (sem distinção de caixa; aceita .SA).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / ticker / description
      Added value: +"Ticker de ação, FII ou ETF da B3, como PETR4, HGLG11 ou BOVA11 (sem distinção de caixa; aceita .SA)."
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the supplied annotations (readOnly, idempotent, non-destructive, closed-world), the description discloses the data source (COTAHIST B3 plus registered proventos), window boundary behavior (ends at last close), benchmarks used (IBOV, IFIX for FIIs, Selic target), the absence of costs and taxes, and edge-case behavior for empty windows and unknown/renamed tickers. That is materially more than the annotations carry.

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?

Front-loaded with the core purpose and organized under labeled sections ('Use quando', 'NÃO use para', 'Fonte', 'Retorna'), so an agent can scan it quickly. Slightly redundant at the tail, where 'Acesso: Aberta, sem chave' restates the free-access point already implied by the source line.

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?

Although no output schema exists, the description names the return fields (`texto` in markdown, `url`, `citacao`) and their content. Combined with source, formula, benchmark, and error semantics, an agent has everything needed to call this single-parameter tool 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%, so the baseline is 3; the description adds that the ticker may be any ação, FII, or ETF and that legacy codes follow corporate renames automatically, which is behavior the schema does not express. It stops short of adding any new format detail, hence 4 rather than 5.

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 computation (what R$ 1.000 became) over named asset classes (ação, FII, ETF) across explicit windows (1, 3, 5, 10 anos) with and without reinvested dividends. This is precise enough to separate it from `desempenho`, `dividendos`, and the ranking tools 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?

Provides three concrete 'Use quando' example queries and an explicit 'NÃO use para' routing rule pointing to `desempenho` for custom date ranges and `dividendos` for dividends only. The when/when-not/alternative triad is fully covered.

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