Skip to main content
Glama

reapresentacoes

Compare original and restated B3 financial statement values by affected account, with both publication dates, to audit history changes and verify backtest revisions.

Instructions

Balanços que a empresa republicou depois, com as duas versões lado a lado.

Quando uma companhia reapresenta um exercício já publicado, o número
antigo costuma sumir das bases — aqui ele fica. Devolve, por conta
afetada, o valor da versão original e o da versão nova, com as datas das
duas publicações. Serve para auditar mudança de histórico e para saber se
um backtest rodou sobre números que depois foram revistos.

Parâmetros:
  ticker — código da ação na B3, em maiúsculas e com o dígito da classe.
    Exemplos: "WEGE3", "PETR4", "SANB11". Veja `listar_empresas`.
  chave_api — chave do Dados B3 (grátis, 200 consultas/dia, sem cartão).
    Dispensável para WEGE3, aberta em todas as ferramentas; necessária para
    as demais. Deixe "" para usar a variável de ambiente DADOS_B3_API_KEY,
    quando existir.

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

Input Schema

NameRequiredDescriptionDefault
tickerYes
chave_apiNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.1

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose meaningful behavior: the return is broken out per affected account with both the original and revised values and both publication dates, and the API key has a 200 queries/day free limit with WEGE3 usable without a key. It omits what happens when a ticker has no restatements and says nothing about ordering or result size.

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?

The purpose is front-loaded in the first sentence and the rationale follows before a clearly separated parameter block. It is longer than strictly necessary — the rate-limit and card-free details are somewhat verbose — but each sentence carries usable information.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read tool with no output schema and no annotations, the description covers purpose, return shape, and both parameters' semantics well enough to call it correctly. The remaining gap is the empty-result case and any note on volume or pagination of restated accounts.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate and does: `ticker` is specified as the B3 code in uppercase with the class digit plus three concrete examples and a pointer to `listar_empresas`, and `chave_api` is explained including its free tier, rate limit, which ticker needs no key, and the environment-variable fallback for empty strings.

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?

The description names a precise resource and shape: restated financial statements returned as old and new versions side by side, per affected account. It also implicitly separates itself from ordinary statement tools by stating that the old number usually disappears from the databases but is preserved here, which lets an agent distinguish it from siblings like fatos_contabeis.

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?

It gives clear usage contexts — auditing historical changes and checking whether a backtest ran on numbers later revised — plus a pointer to `listar_empresas` for obtaining tickers. It does not explicitly say when not to use it or name a competing sibling tool, so it falls short of full when/when-not guidance.

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