Skip to main content
Glama

Reapresentações de balanço

reapresentacoes
Read-onlyIdempotent

Balanços REPUBLICADOS: quando a empresa mudou um número já entregue, as duas versões lado a lado. Use quando: "a Americanas reapresentou o balanço?"; "quais contas da empresa mudaram na republicação?". NÃO use para: as contas vigentes → fatos_contabeis; bandeira de confiança do resumo → veredito. Fonte e fórmula: DFP original × republicada na CVM, conta a conta; nunca corrigido em silêncio. Retorna: linhas {ano, conta CVM, valor antigo, valor novo, variação}. Vazio ou erro: lista vazia = nenhuma republicação com número alterado. Acesso: WEGE3 sem chave; demais tickers exigem chave_api (grátis ou Pro).

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
tickerYesCódigo de AÇÃO na B3, ex.: PETR4, VALE3, ITUB4. Aceita petr4, PETR4.SA, BVMF:PETR4, PETR4F (fracionário) e código antigo (vira o atual). Código de FII, ETF ou BDR devolve erro com `tente_assim`.
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. Changed2 schema fields changed
    • changedInput schema / properties / ticker / description
      Previous value: -"Ticker da B3, como PETR4, VALE3 ou WEGE3 (sem distinção de caixa; aceita o sufixo .SA)."New value: +"Código de AÇÃO na B3, ex.: PETR4, VALE3, ITUB4. Aceita petr4, PETR4.SA, BVMF:PETR4, PETR4F (fracionário) e código antigo (vira o atual). Código de FII, ETF ou BDR devolve erro com `tente_assim`."
    • addedInput schema / properties / ticker / examples
      Added value: +[
      +  "PETR4",
      +  "VALE3",
      +  "ITUB4"
      +]
  2. Changed2 schema fields changed
    • 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 / ticker / description
      Added value: +"Ticker da B3, como PETR4, VALE3 ou WEGE3 (sem distinção de caixa; aceita o sufixo .SA)."
  3. Added

TDQS

A4.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is given. The description nonetheless adds real context beyond them: the data source and comparison formula (DFP original vs. republished on CVM, account by account, 'nunca corrigido em silêncio'), the empty-result semantics, and an access rule (WEGE3 free, other tickers need chave_api). Useful, but it is scoping and provenance rather than undisclosed operational behavior.

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?

Labeled blocks (definition, when to use, when not to use, source, return shape, empty/error, access) put the highest-value information first with no filler sentences. Each line carries distinct decision-relevant content.

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?

For a two-parameter read-only tool with no output schema, the description covers return fields ({ano, conta CVM, valor antigo, valor novo, variação}), empty-result behavior, provenance, and the authentication split between tickers. Nothing an agent needs in order to call it correctly and interpret the result is missing.

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 ticker format rules are already documented in the schema. The description still adds meaning the schema defers to it for: it resolves the chave_api ambiguity by stating which ticker works without a key ('WEGE3 sem chave; demais tickers exigem chave_api'), which the schema description explicitly points back to the tool description for.

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 opens with a precise verb+resource framing: restated financial statements showing 'as duas versões lado a lado' when a company changed an already-delivered number. It explicitly separates this from `fatos_contabeis` (current figures) and `veredito` (confidence flag), so an agent can distinguish it from siblings 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?

It gives concrete trigger phrases ("a Americanas reapresentou o balanço?", "quais contas mudaram na republicação?") plus an explicit 'NÃO use para' section naming the correct alternative for each excluded case. Both the when and the when-not are 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.