Skip to main content
Glama
Sign In

Dados B3

by io.github.Val7h
OverviewDiscussionsAdmin

Histórico de preços

precos
Read-onlyIdempotent

Série DIÁRIA de preços de uma AÇÃO numa chamada só (abertura, máxima, mínima, fechamento, médio, volume, quantidade, negócios), do COTAHIST da B3, do mais antigo ao mais recente. de/ate em AAAA-MM-DD recortam; limite (padrão 1500, máximo 20000) corta a partir do mais antigo e avisa.

O preço NÃO é ajustado: os eventos societários do período vêm junto (eventos) para quem monta o retorno total. WEGE3 gratuita; demais tickers SEM chave devolvem uma AMOSTRA (últimos 30 pregões) com um aviso que diz como ter a série inteira (chave grátis em chave_api) e que desempenho responde sem chave; com chave, a série completa.

★ FORMATO COMPACTO (04/10/2026). Cinco anos de série completa pesam ~250 KB, mais do que cabe no contexto de um cliente de IA (o ChatGPT recebeu os 1.248 pregões e não conseguiu processá-los). Por padrão a resposta traz só data,fechamento em forma de colunas (colunas + linhas, ~28 KB). Peça mais com campos (lista separada por vírgula entre data, ticker, abertura, maxima, minima, fechamento, medio, volume, quantidade, negocios) ou campos="todos" para a lista completa de objetos em serie.

Input Schema

NameRequiredDescriptionDefault
deNo
ateNo
camposNodata,fechamento
limiteNo
tickerYes
chave_apiNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / campos
      Added value: +{
+  "default": "data,fechamento",
+  "title": "Campos",
+  "type": "string"
+}
  2. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds substantial behavior an agent cannot infer: the unadjusted-price caveat, the 30-session keyless sample plus `aviso`, the ~250 KB context-overflow risk, and the default compact column format versus `campos` full objects. This is exactly the extra context the annotations do not carry.

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 purpose and scoping are front-loaded, but the block is long and the final compact-format paragraph is dense with parenthetical detail and a dated release note. Every sentence does carry information, so it is efficient rather than padded, though tighter phrasing would help scanning.

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 6-parameter tool with no output schema and no annotation-derived return info, the description covers param semantics, quota behavior, response size, default versus full output shape, and cross-tool routing. Nothing needed to invoke it correctly is left out.

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 carries the full burden and does so well: `de`/`ate` as AAAA-MM-DD clipping, `limite` default 1500 / max 20000 with oldest-first truncation and a warning, `campos` as an enumerated comma list plus the `todos` special value, and `chave_api` as the free key. Every parameter is given meaning beyond its type.

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 names a specific verb and resource: a DIÁRIA price series for a single stock, from B3's COTAHIST, oldest to newest, with the exact fields returned (abertura, máxima, mínima, fechamento, médio, volume, quantidade, negócios). It is trivially distinguishable from siblings like eventos, dividendos and desempenho.

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 gives strong routing context: `eventos` exists for whoever builds total return on the unadjusted price, and `desempenho` answers without a key. It also explains the keyless sample fallback and how to obtain a free key. What is missing is an explicit negative condition (when to prefer a different sibling over this one) beyond these hints.

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

All Dados B3 toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources