Skip to main content
Glama

multiplos

Retrieves point-in-time valuation multiples (P/E, P/B, EV/EBITDA and quarterly P/E TTM) for a B3 company, using prices after earnings publication to prevent look-ahead bias in backtests.

Instructions

Múltiplos de avaliação ponto-no-tempo de uma empresa da B3.

Devolve P/L, P/VP e EV/EBITDA por exercício, mais P/L TTM por trimestre.

O preço usado é o do primeiro pregão A PARTIR da data real de publicação
do balanço (na maioria dos casos, o próprio dia da entrega) — não o
fechamento do exercício, que ninguém conhecia naquela data. É essa escolha que elimina o look-ahead e permite usar a série em
backtest sem contaminar o passado.

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 — 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": "multiplos"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYes
chave_apiNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and does so thoroughly: it discloses the point-in-time price convention, why it avoids look-ahead bias, the exact metrics returned, rate limits for anonymous and keyed access, AI-assistant-specific limits, and the environment-variable fallback. This is rich behavioral context beyond what the schema supplies.

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?

The description is front-loaded with the tool's core purpose, then structured into a clear methodology paragraph and a parameters section. Every sentence adds useful information about behavior, limits, or parameter handling, with no redundant restatement of the schema.

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 tool without an output schema or annotations, the description covers purpose, methodology, returned metrics, parameter formats, rate limits, and authentication fallback. Nothing an agent needs in order to call it correctly appears to be missing.

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 entirely. It does: ticker format is specified as uppercase with class digit, examples are given (WEGE3, PETR4, SANB11), a reference to listar_empresas is provided, and chave_api is explained as optional with rate-limit consequences and an environment-variable default.

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 states a specific verb and resource: point-in-time valuation multiples for a B3 company, and enumerates the exact metrics returned (P/L, P/VP, EV/EBITDA by fiscal year, plus P/L TTM by quarter). This clearly distinguishes it from sibling tools such as indicadores_anuais or scores.

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 explains the intended use case (backtesting without look-ahead contamination) and provides operational guidance for the ticker parameter and API key. It does not explicitly state when to prefer a sibling tool, but the usage context is clear enough to select it correctly.

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