Skip to main content
Glama
Val7h

dados-b3-mcp

fiis

Screen Brazilian real estate investment trusts by price-to-book and 12-month dividend yield ranges, with optional segment, minimum investor, and result limits to find matching opportunities.

Instructions

Filtra os fundos imobiliários por faixas de P/VP e dividend yield.

Todos os parâmetros são opcionais; sem nenhum, devolve o universo ordenado.

Parâmetros:
  pvp_min / pvp_max — faixa de P/VP. Ex.: pvp_max=1.0 para fundos abaixo do
    valor patrimonial.
  dy_min / dy_max — faixa de dividend yield de 12 meses, em FRAÇÃO:
    dy_min=0.10 significa 10% ao ano, não 10.
  segmento — segmento CVM, casando exato (sem caixa). Ex.: "Shoppings".
  cotistas_min — piso de cotistas, para tirar fundo ilíquido. Padrão 5000.
  limite — quantos devolver (padrão 50, teto 200).
  chave_api — obrigatória: o filtro varre o universo inteiro, não há
    degustação possível.

Só entra número LIMPO: um P/VP ou DY marcado com flag não é tratado como
valor filtrável, e o fundo simplesmente não casa aquele filtro — em vez de
entrar na lista com um número em que nós mesmos não confiamos. Não é
recomendação de investimento.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dy_maxNo
dy_minNo
limiteNo
pvp_maxNo
pvp_minNo
segmentoNo
chave_apiNo
cotistas_minNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.1

TDQS

A4.8/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 so thoroughly: mandatory chave_api, full-universe scan, defaults/caps, exact segment matching, the dirty-number policy, and the investment disclaimer. This is well beyond a minimal read-filter description.

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?

The main purpose is front-loaded, followed by a tight parameter list and a single caveat paragraph. Each sentence adds information—there is no filler or repetition of schema titles.

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 an 8-parameter tool with no output schema and no annotations, the description covers behavior, defaults, required key, matching exactness, and disclaimers. The only minor omission is explicit return-shape details, but 'devolve o universo ordenado' gives enough context for correct invocation.

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 coverage is 0%, but the description documents every parameter with units, defaults, examples (pvp_max=1.0, dy_min=0.10, 'Shoppings'), and edge semantics such as dy being a fraction. It fully compensates for the schema's bare defaults.

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 opening sentence states a specific verb and resource: filters real estate funds (FIIs) by P/VP and dividend yield ranges. It also clarifies that with no parameters it returns the full ordered universe, preventing confusion with single-fund lookup tools like fii.

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?

The description clearly defines when to use the tool: filtering FIIs by P/VP, dividend yield, segment, and liquidity, including the no-params behavior. It does not explicitly contrast it with sibling tools (e.g., fii or screener), so a small alternative-routing gap remains.

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