Skip to main content
Glama

OBM - Open Brazil Market

O que há dentro: carteira, composição, imóveis

obm_get_holdings
Read-onlyIdempotent

Carteira de ETF, composição de índice ou imóveis de FII. Use limit para estreitar.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
as_ofNoData da composição; só índices.
limitNoItens: top N da carteira (ETF) ou linhas por página (índice); padrão 50.
asset_typeYes
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.3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is fully covered. The description adds only that the returned content varies by asset class, and nothing about pagination continuation, default sizing, or identifier requirements 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 clauses with zero filler and the content variation front-loaded before the parameter hint. The missing verb makes the opening a fragment rather than a clean statement, but nothing is redundant or buried.

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 exists, so return values need not be explained, and the schema documents page, as_of and limit well. However, for a 5-parameter read tool with siblings that also retrieve asset data, the description does too little to situate its use, leaving a gap the structured fields cannot fill.

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 60%, and the description compensates by explaining what asset_type values actually yield, which the enum alone does not convey. The limit note restates the schema's own, more detailed limit description, and page/as_of are left entirely to the schema, so it adds partial rather than complete value.

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 three concrete payloads the tool returns (ETF portfolio, index composition, FII real-estate holdings), which lets an agent map the asset_type enum to expected content. The verb is only implicit (a bare noun phrase), and no sibling such as obm_get_asset or obm_list_assets is contrasted, so it falls short of 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 Guidelines2/5

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

The only guidance is 'Use limit para estreitar', which is a parameter hint rather than a when-to-use rule. There is no statement of when to pick this over obm_get_asset or obm_list_assets, and no exclusions or 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