Skip to main content
Glama

Listas com data (resposta pronta)

listas
Read-onlyIdempotent

A lista pronta com data-base: maiores pagadoras de dividendos, ações com P/L abaixo de 10 e FIIs de maior rendimento. Use quando: "quais ações mais pagaram dividendos nos últimos 12 meses?"; "ações com P/L abaixo de 10"; "FIIs que mais pagam". NÃO use para: filtro próprio de ações → screener; filtro próprio de FIIs → screener_fiis; rankings de P/VP de FII → fiis_ranking; dividendos de uma ação → dividendos. Fonte e fórmula: a mesma conta das páginas dadosb3.com/listas: liquidez mínima de R$ 5 mi/dia em 63 pregões, teto de 30% de DY marcado, uma classe por empresa; FIIs com 5.000 cotistas. Retorna: nome, data-base, critério, linhas {ticker, valores}, fonte e source_url para citar. Vazio ou erro: lista vazia devolve o catálogo; nome desconhecido devolve erro com as válidas (dividendos, pl, fiis). Acesso: ABERTA: qualquer ticker, sem chave, um por vez (sem chave: 2000 consultas por hora e 20000 por dia, por endereço; com chave_api vale o limite da chave). Traz citacao: cite-a ao usar o número.

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": "listas"
  }
}

Input Schema

NameRequiredDescriptionDefault
listaNoQual lista: "dividendos", "pl" ou "fiis". Vazio = o catálogo das três.
limiteNoQuantidade de linhas, inteiro de 1 a 20 (padrão 20).
chave_apiNoChave de API opcional. Vazia = acesso aberto: a descrição da ferramenta diz se devolve amostra ou exige chave (chave grátis, sem cartão).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / lista / enum
      Added value: +[
      +  "",
      +  "dividendos",
      +  "pl",
      +  "fiis"
      +]
  2. Changed3 schema fields changed
    • addedInput schema / properties / chave_api / description
      Added value: +"Chave de API opcional. Vazia = acesso aberto: a descrição da ferramenta diz se devolve amostra ou exige chave (chave grátis, sem cartão)."
    • addedInput schema / properties / limite / description
      Added value: +"Quantidade de linhas, inteiro de 1 a 20 (padrão 20)."
    • addedInput schema / properties / lista / description
      Added value: +"Qual lista: \"dividendos\", \"pl\" ou \"fiis\". Vazio = o catálogo das três."
  3. Added

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, yet the description still adds substantial context beyond them: the exact computation methodology (R$ 5 mi/day liquidity over 63 sessions, 30% DY cap, one class per company, 5,000 FII quotaholders), empty-result versus unknown-name error behavior, and rate limits (2000/hour, 20000/day per address, or the key's limit with chave_api). It also states the citation obligation. No contradictions with the annotations.

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?

Dense but rigorously labeled (Use quando / NÃO use / Fonte e fórmula / Retorna / Vazio ou erro / Acesso), so an agent can scan to the section it needs. The routing exclusions are front-loaded and no sentence is filler; even the rate-limit and citation notes are 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 shape itself (nome, data-base, critério, linhas {ticker, valores}, fonte, source_url) and adds error-path and access/quota semantics. Nothing an agent needs to call this correctly and cite the result 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?

Schema description coverage is 100%, so the baseline is 3 and the schema already documents all three parameters. The description goes beyond it by explaining the non-obvious enum behavior — that empty `lista` returns the three-list catalog and that an unknown name errors out with the valid values — which the schema's enum alone does not convey.

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 concrete artifact: a ready-made, dated list covering three named universes (top dividend payers, P/L under 10, highest-yield FIIs). It explicitly names the sibling tools it is NOT (screener, screener_fiis, fiis_ranking, dividendos), so an agent can route without opening any schema.

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?

Contains an explicit 'Use quando' block with three literal user-phrasings mapped to this tool, plus a 'NÃO use para' block that routes four adjacent needs to their correct siblings. This is the full when/when-not/alternative triad with nothing left to inference.

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.