Skip to main content
Glama

OBM - Open Brazil Market

Indicadores e demonstrações de ações

obm_get_financials
Read-onlyIdempotent

Indicadores fundamentalistas por período e demonstrações financeiras de ações, com o link do documento na CVM. Estreite com statement_type ou period_end.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
viewNofundamentals: indicadores por período; statements: demonstrações, com o link do documento na CVM.fundamentals
periodsNoPeríodos de fundamentals (padrão 12).
page_sizeNo
asset_typeNoequities
identifierYesTicker, código de índice ou CNPJ de 14 dígitos (fundos), como na API.
period_endNoData-base da demonstração; só em statements.
statement_typeNoDemonstração específica; só em statements.

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 a closed world, so the safety profile is fully covered. The description adds that statements include the CVM document link, which is useful output context, but it says nothing about pagination behavior, defaults, or result size limits beyond what the schema states.

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 short sentences, front-loaded with the resource scope before the narrowing hint. The CVM document link detail is repeated from the view enum description, and the narrowing sentence is terse enough to be slightly ambiguous about which parameters apply to which view.

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?

An output schema and full annotations mean the description need not explain returns or safety, and it correctly identifies the two views. However, for an 8-parameter tool with only 63% schema coverage, it leaves the agent to infer that period_end and statement_type are inert in fundamentals mode and says nothing about identifier variants such as CNPJ.

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 63%, so roughly a third of the parameters carry no in-schema explanation. The description clarifies that statement_type and period_end act as narrowing filters tied to the statements view, which is modest added meaning, but it says nothing about identifier formats, page_size limits, or the periods default.

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 two resources precisely: fundamentalist indicators by period and financial statements for equities, plus the CVM document link in the payload. An agent can tell it returns per-period fundamentals or full statements. It does not explicitly contrast itself with siblings such as obm_get_asset or obm_get_holdings, which keeps it from a 5.

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?

The second sentence gives a narrowing hint: use statement_type or period_end. That implicitly tells the agent those filters belong to the statements path, but there is no explicit statement of when to choose this tool over obm_get_asset or obm_get_holdings, nor any prerequisites.

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