Skip to main content
Glama

Resumo do mercado hoje

hoje
Read-onlyIdempotent

O que mudou no mercado brasileiro nos últimos 30 dias: balanços entregues, proventos aprovados, eventos e trocas de ticker. Use quando: "o que aconteceu com a empresa X esta semana?"; "quais empresas divulgaram balanço este mês?"; "trocas de ticker recentes". NÃO use para: texto de fato relevante → fatos_relevantes; histórico de dividendos → dividendos. Fonte e fórmula: CVM (entregas e reenvios), B3 (proventos, eventos, códigos) e informes de FII. Retorna: seções balancos, reenvios, proventos, rendimentos_fii, informes_fii, eventos, trocas, cada uma com dados_ate. Vazio ou erro: seção vazia = nada na janela; dados_ate antigo = fonte parada, não mercado parado. Acesso: Gratuita, sem chave.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "hoje"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds substantive context beyond them: the data provenance (CVM entregas/reenvios, B3 proventos/eventos/códigos, informes de FII) and the crucial failure semantics — an empty section means nothing in the window, while a stale `dados_ate` means the source stopped, not the market. It also states access is free with no key.

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?

Front-loaded with the core statement, then labeled blocks (Use quando / NÃO use / Fonte / Retorna / Vazio ou erro / Acesso) that an agent can scan quickly. No filler sentences; even the caveat about stale `dados_ate` is actionable.

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?

With no output schema, the description carries the return contract and does so by naming every section (`balancos`, `reenvios`, `proventos`, `rendimentos_fii`, `informes_fii`, `eventos`, `trocas`) and the shared `dados_ate` field. Combined with the error-state guidance, nothing needed to call or interpret this tool is missing.

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 tool takes zero parameters, so the schema imposes no semantic burden and the baseline is 4. The description correctly says nothing about inputs, though it could have noted there is no filtering/window argument available.

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?

Opens with a specific scope statement: what changed in the Brazilian market over the last 30 days, then enumerates the contents (balanços entregues, proventos aprovados, eventos, trocas de ticker). An agent can distinguish it from siblings like `eventos` or `dividendos` purely from this sentence.

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?

Provides an explicit "Use quando" block with three concrete example questions and a "NÃO use para" block that routes to named alternatives (`fatos_relevantes`, `dividendos`). This is the full when/when-not/alternative pattern.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.