Skip to main content
Glama

Brazilian Insider Trading

GetBrazilianInsiderTrading
Read-only

Insider trading in a company listed on B3, for one B3 listing written BVMF:TICKER (e.g. BVMF:WEGE3), from the monthly reports the company files for its insider bodies from 2018: the controlling shareholders, board of directors, executive officers, fiscal council and other statutory bodies, each with their related persons. Each body files as one, so no person is named. Returns the monthly totals per body in shares and units (bought, sold, the net value in reais and the holding at the month's end; a month with no purchase or sale by a body is left out), then every transaction in any of the company's own securities, newest first: options, debentures and stock loans included, each with its date, body, kind, security, signed quantity, price and value in reais. For a US listing's SEC Form 4 filings use GetInsiderTransactions.

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

Input Schema

NameRequiredDescriptionDefault
offsetNoTransactions to skip for paging (default 0).
tickerYesB3 listing symbol BVMF:TICKER, e.g. BVMF:WEGE3. A bare ticker names a US listing and is answered with the company's B3 listings to ask with.
maxMonthsNoMaximum monthly rows, newest month first (default 12, max 100).
maxResultsNoMaximum transactions, newest first (default 20, max 100).
monthOffsetNoMonthly rows to skip for paging back through older months (default 0).

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 establish readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered; the description goes further by disclosing the data source, the 2018 start of coverage, that bodies file as one and no person is named, that zero-activity months are omitted, and that transactions are ordered newest first. It does not mention rate limits or data-latency caveats, but the omissions/ordering disclosures are the meaningful behavioral traits here.

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?

Purpose is front-loaded in the first clause and every clause carries information, but it is delivered as two long run-on sentences dense with parentheticals and semicolons, making it harder to scan than it needs to be. Structure could be improved by breaking the return-value inventory into a short list.

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?

There is no output schema, so the description carries the return-value burden itself, and it does: monthly totals per body (bought, sold, net reais, month-end holding) followed by itemized transactions with date, body, kind, security, signed quantity, price and value. For a five-parameter read tool that is complete enough to call correctly and interpret the result.

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 description coverage is 100%, and the schema already spells out offset, maxMonths, maxResults and monthOffset with defaults and caps, so the baseline of 3 applies. The description reinforces the ticker format and the 'one listing' constraint, but adds no paging or format semantics beyond what the schema states.

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 resource (insider trading for a company listed on B3), the exact ticker format (BVMF:WEGE3), the source (monthly reports filed by insider bodies from 2018) and the covered bodies. It explicitly distinguishes itself from GetInsiderTransactions, which covers US SEC Form 4 filings, so an agent can separate the two without opening 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 tool and the condition that selects it: 'For a US listing's SEC Form 4 filings use GetInsiderTransactions.' It also warns that a bare ticker names a US listing and will be answered with the company's B3 listings to retry with, which is exactly the failure mode an agent needs to anticipate.

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.