Skip to main content
Glama

Brazilian Company Board and Executive Pay

GetBrazilianManagement
Read-only

Get the board of directors, executive officers and fiscal council of a company listed on B3, and what each body is paid, for one B3 listing written BVMF:TICKER (e.g. BVMF:VALE3), as the company's newest reference form states them. Each body lists a person once, with the highest office they hold there (CEO, CFO, chair, independent member and so on), whether a board seat is independent, the date their first term began and whether the controlling shareholder nominated them. Pay is per body and fiscal year in reais, never per person: average member count, salary and benefits, bonus and profit sharing, share-based, post-employment, termination, other and total, with the highest, average and lowest member's pay, for the past fiscal years and the budget for the year the form covers. For a US listing's executive pay use GetExecutiveCompensation.

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

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.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the description doesn't need to re-establish safety; instead it adds genuine context — the data comes from the company's newest reference form and pay is aggregated per body and fiscal year, never per person. The only gap is nothing about pacing or response size, which matters little for a non-destructive single-entity read.

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

Conciseness3/5

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

The purpose and the alternative are front-loaded, which is good, but the middle is a single sprawling sentence enumerating every pay component (salary, bonus, share-based, post-employment, termination, other, total) without sentence breaks. The enumeration is informative but verbose and hard to scan.

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 carries the full burden of return-value explanation and does so thoroughly: it specifies per-body/per-fiscal-year granularity, the currency (reais), which fiscal years are covered plus the budget year, and the person-level fields (office, independence, first term, controller nomination). Nothing an agent needs to decide whether this tool answers a question is missing.

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 ticker parameter already documents the BVMF:TICKER format, the VALE3 example and the bare-ticker fallback, so the description largely restates structured content. The 100%-coverage baseline of 3 applies.

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 set (board of directors, executive officers, fiscal council and their pay) for a B3-listed company, and explicitly names the sibling GetExecutiveCompensation as the alternative for US listings. An agent can distinguish this from GetExecutiveCompensation, GetBrazilianShareholders and GetExecutiveChanges without opening any 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?

Gives an explicit when-to-use (B3 listing written as BVMF:TICKER) and an explicit when-not (US listing executive pay belongs to GetExecutiveCompensation). It also documents the fallback behavior when a bare ticker is supplied, so the agent knows what to do on a wrong-format call.

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.