Skip to main content
Glama

Brazilian Fund Holdings of a Stock

GetBrazilianFundHoldings
Read-only

Get the Brazilian investment funds holding one B3 share, written BVMF:TICKER (e.g. BVMF:PETR4), from each fund's monthly portfolio, largest position first: the fund and its manager, the month, shares held (counting shares lent out), their value in reais, the position's percentage of the fund's net assets and the change in shares from the fund's previous month. Funds may keep positions confidential for a few months, so each fund answers with its newest month that kept nothing confidential, dated per row; a fund that stopped reporting, or whose newest such month is over a year old, is left out. For US registered funds use GetFundsHoldingStock; for Canadian funds GetCanadianFundHoldings.

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

Input Schema

NameRequiredDescriptionDefault
offsetNoRows to skip for paging (default 0).
tickerYesB3 listing symbol BVMF:TICKER, e.g. BVMF:PETR4. A bare ticker names a US listing and is answered with the company's B3 listings to ask with.
maxResultsNoMaximum funds, largest position first (default 20, max 100).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only say this is a safe open-world read; the description adds genuinely non-obvious behavior: confidential positions cause each fund to answer with its newest non-confidential month, dates are per row, shares include lent-out shares, and results are ordered largest position first. These are exactly the quirks an agent would otherwise misread as missing or inconsistent data.

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 the verb and resource, then the returned fields, then the caveats, then sibling routing — a sensible order. The middle is a long colon-delimited run-on that takes effort to parse, but no sentence is filler.

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 enumerates the returned fields (fund, manager, month, shares, value in reais, percent of net assets, share change) and explains per-row dating, which the agent could not infer elsewhere. For a three-parameter read tool, nothing material is missing.

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 100%, so the baseline is 3; the description earns above that by explaining the result ordering implied by maxResults ('largest position first') and confirming the ticker must be a BVMF: prefixed symbol. It does not add anything about offset/paging beyond the schema, so it stops short of a 5.

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?

Names a specific verb and resource ('Get the Brazilian investment funds holding one B3 share') and pins the identifier format to BVMF:TICKER with an example. It immediately separates itself from the US and Canadian siblings by naming both alternatives at the end.

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

Usage Guidelines5/5

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

Gives explicit routing: this tool for Brazilian B3 funds, GetFundsHoldingStock for US registered funds, GetCanadianFundHoldings for Canadian funds. It also states the inclusion/exclusion rule (funds that stopped reporting or whose newest clean month is over a year old are omitted), so the agent knows what absence of a fund means.

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.