Skip to main content
Glama

fii

Retrieve auditable B3 real estate fund data, including registration, point-in-time P/VP, 12-month dividend yield, vacancy, and recent distributions sourced from CVM monthly reports.

Instructions

Um fundo imobiliário (FII) da B3, com o histórico auditável.

Devolve o cadastro (CNPJ, segmento, mandato, tipo de gestão, público-alvo),
a série de P/VP ponto-no-tempo (preço do 1º pregão a partir da entrega do
informe mensal ÷ valor patrimonial da cota), o dividend yield de 12 meses,
a vacância quando é fundo de tijolo, e os rendimentos recentes.

Rendimento de FII é DISTRIBUIÇÃO DE CAIXA, não lucro — um yield alto pode
ser devolução de capital ou ganho não recorrente. O dado vem dos informes
mensais entregues à CVM, não de agregador.

Parâmetros:
  ticker — código do fundo na B3. Ex.: "MXRF11", "HGLG11".
  chave_api — opcional: qualquer fundo responde sem chave (limite por
    endereço: 60/hora e 150/dia; assistentes de IA, 2.000/hora e 20.000/dia).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ticker": "<ticker>"
    },
    "name": "fii"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYes
chave_apiNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.1

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well: it discloses the data provenance (informes mensais entregues à CVM, not an aggregator), the point-in-time construction of the P/VP series (preço do 1º pregão após entrega do informe ÷ valor patrimonial da cota), and explicit rate limits (60/hora and 150/dia without a key; 2.000/hora and 20.000/dia for AI assistants). The main gap is that it does not say what happens for an unknown ticker or how errors surface.

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?

Front-loaded with the resource, followed by a return-value block, a crucial interpretation warning about yield, then a clearly delimited 'Parâmetros' section. Nearly every sentence earns its place, though 'com o histórico auditável' is a promotional fragment that adds little operational meaning.

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?

No output schema and no annotations exist, so the description must cover both payload and behavior — and it names the returned fields, the provenance, the rate limits and the yield caveat. What remains missing is sibling differentiation and error/invalid-ticker behavior, which are the only material holes for a two-parameter lookup tool.

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 0%, so the description must compensate and largely does: 'ticker' gets concrete B3 examples ("MXRF11", "HGLG11"), and 'chave_api' is explained as optional with the consequence of omitting it spelled out via per-address limits. It stops short of format constraints (6-character alphabetic prefix + digits, case) which the examples only imply.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States the resource precisely: a single B3 real-estate fund (FII) record, then enumerates the returned payload (CNPJ, segmento, mandato, tipo de gestão, público-alvo, série de P/VP, dividend yield 12m, vacância, rendimentos). That is far more specific than a name restatement. However, it never distinguishes itself from siblings such as 'fiis', 'fiis_ranking' or 'desempenho_fii', so an agent must infer that this is the single-ticker lookup.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: the required 'ticker' parameter makes clear this is a per-fund lookup, and the parameter block implies 'use when you have one ticker'. But there is no explicit when-to-use / when-not-to-use guidance and no routing to alternatives like 'fiis' (likely the list) or 'desempenho_fii' (likely performance).

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