Skip to main content
Glama

OBM - Open Brazil Market

Listar ativos de uma classe

obm_list_assets
Read-onlyIdempotent

Lista e filtra ativos de uma classe (bonds: CRI, CRA, debêntures e Tesouro; filtre kind), o ranking de fundos por ano ou as maiores altas e baixas de um índice. Até 100 linhas por página; estreite com filtros ou continue com page.

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>"
    },
    "name": "obm_list_assets"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoTipo: FI, FIDC ou FIP (fundos); tipo do papel (ações, FIIs); cri,cra,debenture,tesouro separados por vírgula (bonds).
pageNo
viewNolist: ativos da classe; ranking: só fundos (exige year); movers: só índices (exige identifier).list
yearNoAno do ranking de fundos.
groupNoSetor (ações), programa (BDRs), segmento (FIIs), classe (fundos, ETFs) ou família (índices).
queryNoTexto de busca no nome ou ticker.
statusNoStatus do título; só bonds. Use active para títulos vigentes.
managerNoGestora; só fundos.
page_sizeNo
asset_typeYes
identifierNoCódigo do índice, para movers.

Output Schema

NameRequiredDescriptionDefault
dataYes
metaYes
sourceYes
reference_dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is fully covered and output schema exists for return values. The description contributes the 100-row page cap and the continue-with-page tactic, but does not disclose view-specific behavioral constraints beyond what the schema's view field already 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 dense sentences with no filler, and the core capability is front-loaded before the pagination advice. The parenthetical bond-type enumeration is slightly heavy but genuinely helps the agent pick kind values.

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?

For an 11-parameter, multi-view listing tool with annotations and an output schema, the description covers the modes, the page-size ceiling and how to continue. It stops short of explaining which asset_type values pair with ranking vs movers, which the agent must derive from the schema.

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 73%, so most parameters are already documented, including the view/year/identifier dependency. The description's mention of 'filtre kind' for bonds and 'ranking de fundos por ano' echoes the schema rather than adding new meaning such as accepted kind syntax or cross-filter behavior; baseline 3 applies.

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 verb ('Lista e filtra') and resource ('ativos de uma classe') and enumerates the three result modes it can return: class listings (with bonds examples CRI, CRA, debêntures, Tesouro), fund rankings by year, and index movers. This clearly separates it from single-asset or history siblings, though it never names an alternative explicitly.

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?

It gives practical operating guidance ('Até 100 linhas por página; estreite com filtros ou continue com page') so an agent knows how to narrow or paginate. However, it never states when to prefer this over obm_search or obm_get_asset, nor any exclusion conditions, leaving the sibling choice 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