Skip to main content
Glama
Val7h

dados-b3-mcp

by Val7h
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

trimestres

Access quarterly ITR financials for B3-listed companies—revenue, margins, ROE, and prices—to answer questions about the current year or latest quarter.

Instructions

Série TRIMESTRAL de uma empresa da B3: contas da ITR, preço e indicadores.

Use quando a pergunta for sobre o ANO CORRENTE ou sobre o trimestre mais
recente — "como foi o 2T", "a margem melhorou este ano?". A série anual só
responde depois que o exercício fecha, e fica até um ano defasada.

Devolve, por trimestre: as contas publicadas na ITR (receita, resultado
bruto, EBIT, lucro, PL, ativo...), o preço do 1º pregão a partir da
publicação daquela ITR, P/L TTM e P/VP, e os indicadores margem_bruta,
margem_ebit, margem_liquida e roe_ttm no mesmo formato da série anual.

O 4º TRIMESTRE NÃO VEM, e isso é escolha: a ITR publica 1T, 2T e 3T; o
exercício fechado é da DFP. É possível derivar `4T = anual − 9M` (há quem
derive), e não derivamos — número calculado por nós não entra na mesma
lista dos que a companhia reportou. Para o ano fechado use
`indicadores_anuais`.

Instituição financeira (banco/seguradora) recebe só margem líquida e
roe_ttm: não há resultado bruto nem EBIT nesse plano de contas.

Parâmetros:
  ticker — código da ação na B3, em maiúsculas. Ex.: "WEGE3", "PETR4".
  chave_api — chave do Dados B3. Dispensável para WEGE3.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tickerYes
chave_apiNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.1

TDQS

A4.3/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 behavioral disclosure burden. It does this well by listing what is returned per quarter, noting the price is from the first trading session after ITR publication, and explicitly warning that the 4th quarter is not included because it belongs to the annual DFP series. It stops short of a 5 because it does not address error cases, missing data, or API-key/auth behavior.

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 core content is well-structured and front-loaded: purpose first, then usage, then return details, then the important Q4 caveat, then an example. The tail is weaker, with redundant phrasing and placeholders like '[maybe]' and '[???]' that add noise rather than value, so it does not earn a 5.

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?

Given the lack of annotations and output schema, the description covers the most important decision and behavior points: quarterly scope, what data is included, the missing 4th quarter, and the call example. It is not fully complete because parameter semantics are thin and the broken tail leaves some guidance unfinished, but an agent can still invoke and interpret the tool correctly in most cases.

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

Parameters3/5

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

The description shows the call signature 'trimestres(ticker, chave_api)' and an example 'trimestres('WEGE3')', which conveys argument order and that chave_api is optional in practice. However, schema coverage is 0%, and the description does not explain what chave_api is, when it is required, or how ticker should be formatted beyond the example. This is partial compensation, not full.

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 first sentence states the exact deliverable: a TRIMESTRAL series for one B3 company containing ITR accounts, price, and indicators. It also distinguishes itself from the annual series by saying the annual series only answers after the fiscal year closes, so an agent can tell this tool apart from sibling annual-data tools.

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 explicitly says to use this tool when the question is about the current year or the most recent quarter, and gives concrete examples like 'como foi o 2T' and 'a margem melhorou este ano?'. It also clearly states the alternative: 'Para o ano fechado, use a série anual.' This is strong 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.

Deploy Server

Other Tools