Skip to main content
Glama

fundos_informe_diario

Read-onlyIdempotent

Fetches CVM daily reports for Brazilian FIF investment funds by CNPJ, including quota, net assets, subscriptions, redemptions, and shareholder counts over a date range.

Instructions

Informe diário de um fundo financeiro (FIF) na CVM: cota, patrimônio, captação, resgate e cotistas.

cnpj é da classe ou do fundo. Cobre só os FIF: FII, FIDC, FIP e FIAGRO estão em outros conjuntos da CVM, ainda não incluídos. inicio e fim aceitam AAAA-MM ou AAAA-MM-DD (padrão: últimos 3 meses; máximo 12 meses por chamada). detalhe='resumo' (padrão) traz rentabilidade simples, captação líquida e uma linha por mês (último informe do mês, com a captação líquida somada). detalhe='diario' traz cada dia, 60 por página: use pagina (1, 2...). Para fundos com subclasses há uma série por subclasse, ou só a de subclasse. A rentabilidade simples é cota final sobre cota inicial menos 1; não é a rentabilidade oficial (ignora distribuições e taxas).

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": {
      "cnpj": "<cnpj>"
    },
    "name": "fundos_informe_diario"
  }
}

Input Schema

NameRequiredDescriptionDefault
fimNo
cnpjYes
inicioNo
paginaNo
detalheNoresumo
subclasseNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent and openWorld, and the description still adds substantial operational detail: a 12-month maximum window, a default of the last three months, 60 records per page with pagina for paging, and the explicit caveat that the 'rentabilidade simples' figure is computed as final quota over initial quota minus one and is not the official return because it ignores distributions and fees. Those are exactly the kind of traps an agent needs to know about before reporting results.

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?

The definition is front-loaded with purpose and then orders constraints before the mode-specific behavior, with no filler sentences. A few clauses, such as the subclasse sentence, are slightly compressed and take a second read, but nothing is redundant.

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 a read-only six-parameter query with no output schema, the description covers defaults, hard limits, pagination, mode selection, subclass behavior and a caveat about the computed metric. An agent has everything needed to call it correctly and to interpret the numbers it gets back.

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 description coverage is 0%, so the description carries the full burden, and it does: cnpj is the class or fund CNPJ, inicio/fim accept AAAA-MM or AAAA-MM-DD with default and maximum, detalhe has resumo vs diario semantics with the aggregation rule for resumo (last report of the month with net fundraising summed), pagina indexes the daily pages, and subclasse selects a single series when the fund has subclasses.

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 specific resource and scope ('Informe diário de um fundo financeiro (FIF) na CVM') and enumerates the returned data points (cota, patrimônio, captação, resgate, cotistas). It also states the exclusion boundary against other CVM datasets, so an agent can distinguish it from fundos_cvm and the wider series of sibling tools without opening the schema.

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?

It gives explicit negative scope: only FIF are covered, while FII, FIDC, FIP and FIAGRO sit in other CVM datasets that are not yet included. That prevents the most likely misuse. It does not, however, name a specific alternative tool to use for those other fund types, so an agent lacks a concrete fallback route.

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