Skip to main content
Glama

Brazilian Company Filings

GetBrazilianFilings
Read-only

List the documents a company listed on B3 delivered to its securities regulator, for one B3 listing written BVMF:TICKER (e.g. BVMF:WEGE3), newest first, from 2003: material facts, market notices, financial statements, earnings releases, analyst presentations, shareholder meeting documents and its other disclosures. Each row gives the delivery date, the kind of document in English (marked resubmitted when it replaces an earlier one), the company's own description, mostly in Portuguese, and a link that opens the PDF on its Equibles page. Narrow with query, whose words must all appear in the description or kind (e.g. 'material fact', 'dividendos'), and a date range. The documents' text is not searchable: ListFilings, SearchDocuments and ReadDocumentLines cover SEC filings and transcripts, which a Brazilian company has only when it also files with the SEC. For reported figures use GetFinancialStatement.

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

Input Schema

NameRequiredDescriptionDefault
queryNoOptional words (at most 6) that must all appear in the description or the kind of document, in any case, e.g. 'material fact', 'financial statements', 'assembleia'.
offsetNoRows 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.
endDateNoOptional latest delivery date, YYYY-MM-DD.
startDateNoOptional earliest delivery date, YYYY-MM-DD.
maxResultsNoMaximum filings, newest 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 already declare readOnlyHint, non-destructive and closed-world, and the description goes well beyond them: newest-first ordering, coverage starting 2003, the 'resubmitted' marker on replacing documents, English kind labels vs mostly-Portuguese descriptions, and a PDF link hosted on Equibles. It also discloses the key negative behavior that full document text is not searchable, which is exactly the kind of trait annotations cannot express.

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?

It is a dense single paragraph, but it is front-loaded with purpose and scope before alternatives. Nearly every clause carries information (format, ordering, document kinds, query semantics, exclusions); only the enumeration of document types runs slightly long.

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 still tells the agent what each row contains (delivery date, English kind, company description, PDF link), plus ordering, paging defaults and the text-search limitation. Nothing material an agent needs to invoke or interpret the result 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 schema carries the field definitions, but the description adds real meaning: 'query' words must all appear in the description or kind (with examples like 'material fact', 'dividendos'), and a bare ticker 'is answered with the company's B3 listings to ask with', which is behavior the schema only hints at. Date-range narrowing is mentioned but adds little beyond the startDate/endDate schema text.

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?

The description gives a specific verb and resource ('List the documents a company listed on B3 delivered to its securities regulator'), states scope (newest first, from 2003) and enumerates the document classes returned. It also explicitly separates itself from ListFilings, SearchDocuments, ReadDocumentLines and GetFinancialStatement, so an agent can pick it without opening a 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?

It states when to use it (Brazilian B3 issuer disclosures) and when not to: 'The documents' text is not searchable: ListFilings, SearchDocuments and ReadDocumentLines cover SEC filings and transcripts', and 'For reported figures use GetFinancialStatement.' The alternative for a bare ticker is also described, so the routing decisions are all covered.

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.