Skip to main content
Glama

Search Brazilian Funds

SearchBrazilianFunds
Read-only

Find Brazilian investment funds by words of their name, accents optional (e.g. 'previ acoes', 'verde'), or by their 14-digit register number, largest net assets first: each fund's name, manager, asset class, newest reported month, net assets in reais and slug. Pass the slug to GetBrazilianFundPortfolio for the fund's share portfolio. For US registered funds use SearchFunds; for the Brazilian funds holding one B3 share use GetBrazilianFundHoldings.

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": {
      "query": "<query>"
    },
    "name": "SearchBrazilianFunds"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesWords of the fund's name (all must appear, accents optional), or its register number with or without punctuation.
offsetNoRows to skip for paging (default 0).
maxResultsNoMaximum funds, largest net assets first (default 20, max 50).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already cover read-only and closed-world safety, and the description adds real behavioral detail beyond them: accent-insensitive matching, ranking by largest net assets, the newest reported month per fund, and net assets in reais. It stops short of describing empty-result or paging edge behavior, but the added context is substantial.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with what is searched and how results are ranked, then return fields, then routing to related tools. No filler or redundant restatement of the tool name.

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 compensates by enumerating the returned fields (name, manager, asset class, newest month, net assets, slug) and explaining the follow-up call. For a three-parameter search tool this leaves nothing an agent needs unresolved.

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, and the description genuinely adds: accents are optional in query words, register numbers work with or without punctuation, all words must appear, and maxResults returns largest-first. Only the paging interaction of offset with maxResults is left to the schema.

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 verb and resource ('Find Brazilian investment funds') plus both matching modes (name words or 14-digit register number), the sort order (largest net assets first), and the returned fields. It is clearly separable from SearchFunds (US) and GetBrazilianFundHoldings without opening their schemas.

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?

Explicitly routes the agent: use SearchFunds for US registered funds, GetBrazilianFundHoldings for funds holding a single B3 share, and pass the returned slug to GetBrazilianFundPortfolio. Both when-to-use and when-to-use-something-else are spelled out.

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.