Skip to main content
Glama

Brazilian Company Shareholders

GetBrazilianShareholders
Read-only

Get the major shareholders of a company listed on B3, for one B3 listing written BVMF:TICKER (e.g. BVMF:VALE3), as the company's newest reference form states them: holders of 5% or more of a share class, controllers and members of a shareholder agreement, each with common, preferred and total shares and percentages, nationality and marks for controller and agreement, then the company's treasury shares and every other share. A company holder lists the owners behind it, with percentages of that holder's own capital, not of the company's. Also returns issued capital in reais and shares issued, free float, treasury shares and how many individual, company and institutional shareholders the company has. For a US listing's holders use GetAllHolders.

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

Input Schema

NameRequiredDescriptionDefault
tickerYesB3 listing symbol BVMF:TICKER, e.g. BVMF:VALE3. A bare ticker names a US listing and is answered with the company's B3 listings to ask with.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only establish readOnly/openWorld=false and non-destructive, but the description adds real substance: the 5% threshold, inclusion of controllers and agreement members, treasury and other shares, and the non-obvious semantics of a company holder's percentages being of that holder's own capital rather than the company's. It does not mention pagination, caching or freshness limits, which is the only notable gap given there is no output schema.

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 action and the listing format, and the sibling routing is placed last where it belongs. The single enormous sentence and trailing enumeration ('treasury shares and every other share') are heavier than needed, but essentially every clause carries distinct information.

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 must describe the return payload itself, and it does so thoroughly: per-holder fields and percentages, flags, nationality, plus company-level issued capital, free float, treasury and shareholder-type counts. For a single-parameter read tool that is complete.

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 single parameter already documents the BVMF:TICKER format plus the bare-ticker fallback, so the description's repetition of 'BVMF:TICKER (e.g. BVMF:VALE3)' adds nothing new. Baseline 3 is appropriate when the schema carries the full parameter burden.

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 — 'Get the major shareholders of a company listed on B3' — and immediately bounds the scope (one listing, newest reference form). It explicitly routes the US-listing case to GetAllHolders, so the agent can distinguish it from that sibling without reading either schema.

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?

Names the alternative ('For a US listing's holders use GetAllHolders') and the condition that selects it. The ticker parameter description additionally handles the mis-input case (bare US ticker) and states what happens instead, so there is little left to infer.

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.