Skip to main content
Glama

OBM - Open Brazil Market

Ficha de um ativo

obm_get_asset
Read-onlyIdempotent

Identidade e indicadores principais de um ativo; para fundos, view=metrics traz os indicadores. Bonds cobre CRI, CRA, debêntures e Tesouro; o cadastro não traz preços, consulte obm_get_price_history para PU e taxas. Para descobrir Tesouro use obm_list_assets com asset_type=bonds e kind=tesouro; demais ativos podem usar obm_search.

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

Input Schema

NameRequiredDescriptionDefault
viewNodetail: ficha; metrics: indicadores de fundo (só fundos).detail
asset_typeYes
identifierYesTicker, CNPJ ou código do título; Tesouro pode conter espaço, como NTN-B PRINCIPAL_2035-05-15.

Output Schema

NameRequiredDescriptionDefault
dataYes
metaYes
sourceYes
reference_dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/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 covered. The description adds meaningful behavioral context beyond them: the registry ('cadastro') does not carry prices, so this tool will not return PU or rates, which prevents a common wrong invocation. It does not discuss completeness or staleness of the record, keeping it just under 5.

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?

Three dense sentences, each carrying routing or scoping information with no filler, and the core identity/indicators statement is front-loaded. The semicolon-chained clauses make it slightly harder to parse than a clean bullet structure, but nothing is redundant.

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?

Given an output schema exists, the description need not describe return fields, and it covers the critical cross-tool boundaries (prices, Tesouro discovery) that an agent would otherwise get wrong. The main residual gap is that it does not clarify what the 'detail' view returns versus 'metrics' beyond the enum text, but the schema and output schema carry that.

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 67% and the description adds real meaning beyond it: it explains that view=metrics is fund-only and that asset_type=bonds spans CRI, CRA, debêntures and Tesouro. The identifier's space-containing Tesouro format is largely restated from the schema, and asset_type semantics for non-bond types remain undocumented.

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 a specific resource and scope ('Identidade e indicadores principais de um ativo') and differentiates from siblings by pointing price lookups to obm_get_price_history and discovery to obm_list_assets/obm_search. It clarifies that bonds encompass CRI, CRA, debêntures and Tesouro. It stops short of an explicit verb like 'returns' or 'fetches', making it a strong but not perfect 5.

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?

Explicit when-to-use guidance is present: view=metrics applies only to funds, price/PU and rates must go through obm_get_price_history, and Tesouro discovery must go through obm_list_assets with asset_type=bonds and kind=tesouro while other assets use obm_search. Each alternative is named together with the condition that selects it, leaving nothing to inference.

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