Skip to main content
Glama

fatos_contabeis

Retrieves standardized accounting figures for a B3-listed company by period, including revenue, EBIT, net income, equity, cash and debt, each with its CVM account code for audit.

Instructions

Contas contábeis padronizadas de uma empresa da B3, com a origem de cada número.

Devolve, por período: receita, EBIT, lucro líquido, patrimônio líquido,
caixa, dívida bruta e dívida líquida, entre outras — e, junto de cada
valor, o código da conta CVM de onde ele saiu, para auditoria.

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`.
  trimestral — escolhe a granularidade da série, e só isso. False (padrão)
    devolve os exercícios ANUAIS, vindos dos formulários DFP; True devolve
    os TRIMESTRES, vindos dos ITR. Não é um filtro: os dois modos cobrem o
    mesmo histórico, muda apenas o período de cada linha.
  chave_api — opcional. Sem chave, qualquer ticker responde, um por vez
    (limite por endereço: 60/hora e 150/dia; assistentes de IA, 2.000/hora
    e 20.000/dia); com chave vale o limite da chave. 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": "fatos_contabeis"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYes
chave_apiNo
trimestralNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the anonymous rate limits (60/hour, 150/day), the elevated AI-assistant limits (2,000/hour, 20,000/day), the API-key fallback to DADOS_B3_API_KEY, and that annual data comes from DFP forms while quarterly comes from ITR. It does not cover error behavior for invalid tickers or data freshness/caching.

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 what is returned and how provenance works, then a clearly delimited `Parâmetros:` block per argument. It is long, but the length is justified by the complete absence of schema descriptions; wording is tight with no filler.

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 tool with no annotations, no output schema, and 0% schema coverage, the description supplies return contents, provenance metadata, all three parameters, and access limits. Remaining gaps are minor: historical coverage start and error/empty-result behavior are unstated.

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 fully compensate, and it does: ticker format is pinned down with uppercase and class digit plus concrete examples (WEGE3, PETR4, SANB11), `trimestral` is explained as a granularity switch sourced from DFP vs ITR rather than a filter, and `chave_api` is documented with default-empty semantics and environment-variable fallback.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — returns standardized accounting accounts for a B3 company, with the CVM account code behind each number — and enumerates the fields returned (revenue, EBIT, net income, equity, cash, gross/net debt). It differentiates weakly from close siblings such as indicadores_anuais or multiplos, but the provenance/audit framing gives it a distinct identity.

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

Usage Guidelines3/5

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

Usage is largely implied: it points to `listar_empresas` for valid tickers and explains that `trimestral` is not a filter, but it never says when to choose this tool over `indicadores_anuais`, `multiplos`, or `trimestres`. No explicit when-not-to-use guidance is offered.

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