Skip to main content
Glama
Val7h

dados-b3-mcp

by Val7h
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

hoje

Get a 30-day recap of B3-listed companies: balance-sheet filings, restatements, dividends, FII income, corporate actions, and ticker changes, each dated by source.

Instructions

O que mudou no mercado brasileiro nos últimos 30 dias.

Responde "o que aconteceu com a empresa X esta semana" — a pergunta que
nenhuma série anual responde. Devolve, na janela: os balanços que ficaram
públicos (com a data de entrega à CVM), os documentos REENVIADOS (versão
maior que 1: a companhia republicou o que já tinha entregue), os proventos
de ações aprovados, os rendimentos e informes de FII, os eventos
societários (grupamento, desdobramento, bonificação) e as trocas de ticker.

Cada seção declara `dados_ate`: a data máxima daquela FONTE. As defasagens
são diferentes — a CVM entrega documento com dias de atraso, a B3 publica
rendimento de FII quase no dia — e a janela é fixa a partir de hoje, então
uma fonte parada aparece como parada em vez de parecer recente.

Sem parâmetros. Gratuito — não exige chave.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.1

TDQS

A4.5/5.0
Behavior5/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 exceptionally well: it discloses source-specific lag, explains `dados_ate` and the difference between CVM and B3 publication delays, defines version>1 as re-submission semantics, and mentions that no API key is required. It also clearly implies a read-only operation by saying it 'devolve' data.

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 description is front-loaded with the main purpose and organized into content categories, data-freshness behavior, and invocation notes. It is slightly longer than strictly necessary due to a natural-language flourish, but each paragraph adds distinct operational value.

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 no-parameter, no-output-schema tool, the description is unusually complete: it lists every returned section, explains freshness and lag, and states invocation essentials. The only notable gap is that the example about 'empresa X' could imply company-level filtering, but the tool has no parameters and the description never clarifies whether a specific company can be requested.

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?

The schema is empty with 100% coverage, so there are no parameters to explain. The description reinforces this with 'Sem parâmetros' and adds the useful operational fact that it is free and requires no key, which is appropriate for a zero-parameter tool.

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 a concrete purpose: report what changed in the Brazilian market in the last 30 days. The description then lists the exact categories returned — balanços, documentos reenviados, proventos, rendimentos e informes de FII, eventos societários e trocas de ticker — which clearly distinguishes it from historical/series-oriented sibling tools.

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 identifies the target question ('o que aconteceu com a empresa X esta semana') and explicitly says that annual series do not answer it, signaling use for recent-change discovery. It also notes the window is fixed and the tool has no parameters. However, it does not name the alternative sibling tools or state exactly when not to use them, only implies it.

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