Skip to main content
Glama

Brazilian Fund Share Portfolio

GetBrazilianFundPortfolio
Read-only

Get one Brazilian investment fund's share portfolio for a month, largest value first: each share's company and B3 symbol (when the share is a verified B3 listing), common, preferred or unit, shares held (counting shares lent out, also shown alone), value in reais, percentage of the fund's net assets and change in shares from the fund's previous month; with the fund's manager, asset class, net assets and the months it reported, from 2018. Only shares are listed, never the fund's bonds, fund units or derivatives. Funds may keep positions confidential for a few months, so by default it answers the fund's newest month that kept nothing confidential; a month that kept some confidential lists only part of the portfolio and says so. Find the fund with SearchBrazilianFunds.

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": {
      "fund": "<fund>"
    },
    "name": "GetBrazilianFundPortfolio"
  }
}

Input Schema

NameRequiredDescriptionDefault
fundYesThe fund's slug from SearchBrazilianFunds or GetBrazilianFundHoldings, its register number, or its exact name.
monthNoOptional month, YYYY-MM (e.g. 2026-04). Default: the fund's newest month that kept no share position confidential.
offsetNoRows to skip for paging (default 0).
maxResultsNoMaximum positions, largest value first (default 50, max 100).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare a safe read, yet the description discloses substantial extra behavior: results ordered largest value first, default month selection based on confidentiality, partial portfolios when positions are withheld, historical coverage from 2018, and that lent-out shares are counted. This is exactly the context annotations cannot carry.

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 core verb and resource, and every clause carries information about fields, exclusions, or defaults. The opening sentence is a long run-on that would read better as a short purpose statement followed by field and caveat details.

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?

With no output schema, the description fully enumerates the returned fields (company, B3 symbol, share type, shares held and lent, value in reais, percentage of net assets, month-over-month change) plus fund metadata, and covers the confidentiality edge case an agent must interpret.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema already documents the fund identifier, the YYYY-MM month with its confidentiality-based default, offset, and maxResults with its largest-first ordering. The description largely restates those semantics, adding little beyond what the schema provides.

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?

Specific verb and resource ('Get one Brazilian investment fund's share portfolio for a month') with scope stated up front. It explicitly excludes 'bonds, fund units or derivatives', which separates it from broader holdings tools, and names SearchBrazilianFunds as the fund-lookup path.

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?

Clear context: use this to see a fund's share-level positions for a month, and use SearchBrazilianFunds to find the fund. The scope exclusions (no bonds/units/derivatives) implicitly route the agent elsewhere for those, but no sibling is named as the alternative for non-share holdings.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.