Skip to main content
Glama

indicadores_anuais

Retrieve annual fundamental indicators for a B3-listed company from 2010 onward, including ROIC, ROE, margins, revenue and profit growth, and net debt/EBITDA.

Instructions

Série anual de indicadores fundamentalistas de uma empresa da B3.

Cobre de 2010 até o último exercício publicado e devolve, por ano: ROIC,
ROE, margens (bruta, EBIT e líquida), crescimento de receita e de lucro, e
dívida líquida/EBITDA. Para saber como cada um é calculado, chame
`metodologia`.

Parâmetros:
  ticker — código da ação na B3, em maiúsculas e com o dígito da classe.
    Exemplos: "WEGE3" (ordinária), "PETR4" (preferencial), "SANB11"
    (unit). Use `listar_empresas` para descobrir os disponíveis.
  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": "indicadores_anuais"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYes
chave_apiNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses the historical coverage boundary, the anonymous rate limits per address (60/hora, 150/dia) versus keyed/AI-assistant limits, and the API-key fallback behavior. It omits what happens on an invalid ticker or an exhausted quota, and does not state the shape of the response beyond the metric list.

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?

Purpose and coverage are front-loaded in the first sentence, with a clearly delimited "Parâmetros" block for the per-parameter detail. The long parenthetical on rate limits is dense but load-bearing; overall there is little 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?

No output schema exists, so the description appropriately lists the returned metrics and the time granularity (per year), and it covers both parameters plus quota behavior. Only the precise response structure (e.g., list of per-year objects) and error behavior are left implicit.

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 description coverage is 0%, so the description must compensate and it does: `ticker` is specified as uppercase B3 code with the class digit, with concrete examples for ordinária, preferencial and unit. `chave_api` is fully explained — optional, "" means fall back to DADOS_B3_API_KEY, and it changes which rate limit applies.

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 verb and resource ("Série anual de indicadores fundamentalistas de uma empresa da B3") and then enumerates exactly which metrics come back per year (ROIC, ROE, margens, crescimento, dívida líquida/EBITDA). The word "anual" plus the explicit coverage window (2010 até o último exercício) separates it from quarterly siblings such as `trimestres`.

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?

Routes the agent to two named siblings: `metodologia` for how each indicator is computed and `listar_empresas` for discovering valid tickers. It does not, however, state when to prefer this over adjacent tools like `trimestres`, `multiplos`, or `fatos_contabeis`, so the alternative-selection guidance is partial.

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