Skip to main content
Glama

fiis_ranking

Ranks Brazilian real estate funds by P/VP discount and 12-month dividend yield, and reports segment medians for P/VP, yield, and vacancy.

Instructions

Ranking dos fundos imobiliários (FIIs): os mais descontados (menor P/VP ponto-no-tempo), os maiores pagadores (DY 12m) e a mediana de P/VP, DY e vacância por segmento. Do informe mensal da CVM + COTAHIST, só valores limpos (sem flag) e fundos líquidos. Descritivo, não é recomendação.

Parâmetros:
  chave_api — opcional: o ranking responde sem chave (limite por
    endereço); com chave vale o limite da 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": "fiis_ranking"
  }
}

Input Schema

NameRequiredDescriptionDefault
chave_apiNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses data provenance (CVM monthly report plus COTAHIST), the filtering rules (only unflagged/clean values, only liquid funds), the interpretive caveat that it is descriptive and not investment advice, and the rate-limit behavior tied to the key. It stops short of describing the response shape or whether results are paginated or cached.

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 ranking content before the parameter note, and every clause adds information: metrics, data sources, filters, disclaimer, auth behavior. Slightly dense as a single paragraph in two languages-of-register, but nothing is redundant.

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?

For a zero-required-parameter, read-only ranking endpoint with no output schema, the description supplies what the agent needs to decide to call it and what it will get back conceptually (three ranking views plus per-segment medians). The only real gap is the concrete return structure, which matters little given the tool takes no meaningful input.

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 coverage is 0% and the single property has no description, so the prose must compensate. It does: 'chave_api' is explained as optional, the tool works without it under a per-address limit, and supplying one applies that key's limit — meaning the agent cannot glean from the schema alone. Full marks withheld only because the expected key format/where to obtain it is not stated.

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 concrete resource and three distinct outputs: most discounted FIIs (lowest point-in-time P/VP), largest payers (12m DY), and median P/VP, DY and vacancy per segment. An agent can distinguish this from the sibling tools 'fiis', 'desempenho_fii' and 'etfs_ranking' because the ranked metrics and the unit of aggregation (segment) are spelled out.

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 only implied: the agent can infer this is the tool for cross-sectional FII rankings, and the parameter note explains when to pass a key. But the description never states when to prefer this over 'fiis' or 'desempenho_fii', and there are no explicit exclusions beyond the note that it is descriptive rather than a recommendation.

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