Skip to main content
Glama

fundos_cvm

Read-onlyIdempotent

Query CVM-registered investment funds by name, classification, type, manager, administrator, or target audience, and retrieve full fund details by exact CNPJ.

Instructions

Fundos de investimento registrados na CVM (cadastro público da RCVM 175: classes de cotas).

Filtros: consulta (trecho do nome), classificacao (ex.: Ações, Renda Fixa), tipo (ex.: Fundo de Investimento Imobiliário), gestor, administrador (nome ou CNPJ) e publico_alvo. A lista vem em tabela (colunas: cnpj, nome, tipo, classificacao, gestor, administrador, patrimonio_liquido, data_patrimonio), ordenada pelo patrimônio informado, que pode estar defasado. Com cnpj exato (de classe ou de fundo), devolve a ficha completa: CNPJs e nomes de administrador, auditor, custodiante e controlador, e subclasses. Situação padrão 'Em Funcionamento Normal'; '' inclui todas. Cotas diárias: fundos_informe_diario.

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

Input Schema

NameRequiredDescriptionDefault
cnpjNo
tipoNo
gestorNo
limiteNo
consultaNo
situacaoNoEm Funcionamento Normal
publico_alvoNo
administradorNo
classificacaoNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world behavior, so the bar is lower, and the description still adds real value: it discloses the default 'Em Funcionamento Normal' filter, the shape of the list result (columns), that sorting is by reported net assets which may be stale, and that exact-CNPJ lookups return a richer record with auditor/custodian/controller/subclasses. It omits any note on how `limite` truncates results or how to page past the default.

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-loads what the dataset is, then enumerates filters, then describes result shape and edge behaviors. Dense but every segment carries information; the only slack is the filter list slightly duplicating parameter names already in the schema.

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?

With nine optional parameters and no output schema, the description compensates by describing returned columns and the richer detail-mode payload, plus default filtering semantics. The main gap is the undocumented `limite` (default 15) and no sense of total result size or pagination.

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% with no enums, so the description carries the full burden, and it explains eight of nine parameters with example values (`classificacao`: Ações, Renda Fixa; `tipo`: Fundo de Investimento Imobiliário; `administrador` accepts name or CNPJ; `situacao` default and empty-string semantics). The `limite` parameter is never mentioned in the description, and no allowed values are given for `publico_alvo`.

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?

States a specific resource (CVM-registered investment funds, RCVM 175 share classes) and a specific retrieval behavior, and distinguishes its own two modes: filtered list versus full record when an exact `cnpj` is given. An agent knows exactly what domain this covers 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?

Gives explicit routing for a related need ('Cotas diárias: fundos_informe_diario') and explains the mode switch: pass an exact `cnpj` to get the full ficha instead of a list. It also documents the default `situacao` and that an empty string broadens it. No explicit when-not-to-use guidance is offered beyond the sibling pointer.

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