Skip to main content
Glama

OBM - Open Brazil Market

Estrutura e documentos de fundos

obm_get_fund_filings
Read-onlyIdempotent

Classes, séries e documentos de fundos (cada documento traz source_url) e informes de FIIs. Para séries, descubra class_cnpj com view=classes.

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": {
      "asset_type": "<asset_type>",
      "identifier": "<identifier>"
    },
    "name": "obm_get_fund_filings"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoFim; em series e reports.
pageNo
viewNoFundos: classes, series (exige class_cnpj) ou documents, com source_url (padrão). FIIs: reports (padrão).
startNoInício; em series e reports. Padrão: 12 meses.
subclassNoSubclasse, em series.
page_sizeNo
asset_typeYes
class_cnpjNoCNPJ da classe, para series; veja view=classes.
identifierYesTicker, código de índice ou CNPJ de 14 dígitos (fundos), como na API.

Output Schema

NameRequiredDescriptionDefault
dataYes
metaYes
sourceYes
reference_dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the description's burden is lower. It adds useful behavior context — documents carry source_url and the default view differs by asset_type (documents for funds, reports for FIIs) — but says nothing about pagination limits, date-range defaults, or empty-result behavior beyond what the schema already declares.

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?

Two tight sentences, no filler, with the resource inventory front-loaded and the class_cnpj workflow hint placed second where it is most needed. It could be tighter by using a verb up front instead of a bare noun phrase.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is moderately complex (9 params, enum-driven views, an output schema and annotations already present), so the description does not need to explain return values. It is still incomplete on how asset_type interacts with view when view is omitted, and on what a valid identifier looks like for funds versus FIIs.

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?

With 67% schema coverage across 9 parameters, the schema already documents view, class_cnpj, start, end, page, and identifier. The description mostly restates the view/class_cnpj relationship the schema already encodes ('series (exige class_cnpj)', 'veja view=classes'), adding the two-step discovery hint but no detail on identifier formats, subclass, or date semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the concrete resources returned: fund classes, series, and documents (each with source_url), plus FII reports. It lacks an explicit verb (list/retrieve), but the noun list is specific enough to separate it from siblings like obm_get_asset or obm_get_financials, none of which deal with fund structuring documents.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

One actionable workflow rule is given: to fetch series, discover class_cnpj via view=classes. That is real guidance for the hardest parameter. However, there is no statement of when to choose this tool over obm_get_asset or obm_list_assets, nor any exclusion, so usage remains implied rather than explicit.

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.

Resources