Skip to main content
Glama

OBM - Open Brazil Market

Proventos e eventos

obm_get_income_events
Read-onlyIdempotent

Dividendos, juros sobre capital e desdobramentos de ações, ou rendimentos de FIIs, nos últimos months meses (padrão 12). Bonds: agenda de juros e amortização, sem months.

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_income_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPágina; continue daqui se houver mais.
monthsNoMeses até hoje; padrão 12.
page_sizeNoLinhas por página (máximo 100).
asset_typeYes
identifierYesTicker ou código do título.

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 declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds one genuinely new behavioral fact — that bonds follow a coupon/amortization agenda without the 'months' window — but leaves pagination behavior and the shape of results to the schema and 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.

Conciseness3/5

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

Two short sentences with the event list front-loaded, so it is appropriately sized. However, the duplicated/mixed wording 'nos últimos months meses (padrão 12)' and the trailing 'sem months' are garbled and force the reader to re-parse instead of stating the rule cleanly.

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

Completeness4/5

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

With an output schema present, return values need not be described, and the description covers the main asset-type branches plus the time window. Only minor gaps remain, such as how the events are scoped to the identifier for bonds and the pagination workflow.

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 80%, so the schema already explains page, page_size, months and identifier. The description reinforces the 12-month default and clarifies that 'months' does not apply to bonds, which is a real addition, but it adds nothing about asset_type selection or identifier semantics beyond the schema.

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 concrete resource types (dividendos, juros sobre capital, desdobramentos, rendimentos de FIIs, plus a bond coupon/amortization agenda), so an agent knows this is a corporate-actions/income-event tool rather than a price or returns tool. It does not name any sibling for comparison, and the mixed Portuguese/English phrasing blurs the scope slightly.

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?

Usage is implied by enumeration of what is returned, and one conditional rule is given (bonds use an interest/amortization schedule and ignore 'months'). There is no explicit when-to-use vs when-not guidance and no named alternative (e.g., obm_get_returns or obm_get_price_history) for the cases this tool does not cover.

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