Skip to main content
Glama

OBM - Open Brazil Market

Buscar ativos

obm_search
Read-onlyIdempotent

Busque ticker, nome ou CNPJ nas classes públicas, respeitando seu plano; sem chave, somente os 9 ativos da demonstração. Use page para continuar e estreite query quando houver muitos resultados.

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": {
      "query": "<query>"
    },
    "name": "obm_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPágina; continue daqui se houver mais.
queryYesTicker, nome ou CNPJ.
page_sizeNo
asset_typeNo

Output Schema

NameRequiredDescriptionDefault
dataYes
metaYes
sourceYes
reference_dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context beyond them: results are filtered by the caller's plan, and without an API key only the 9 demo assets are returned — an important scope limit an agent cannot infer from structured fields.

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?

A single dense sentence that front-loads purpose and then appends the auth scope and pagination advice; nothing is redundant. The semicolon-chained clauses make it slightly harder to scan than separate short sentences would.

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?

With an output schema present, return values need no explanation, and the plan/demo-asset restriction is covered. Still missing is any hint about matching semantics (substring vs prefix) or what the asset_type filter does, which matters for a search tool with an undocumented enum parameter.

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 50%: 'query' and 'page' are documented in the schema, and the description reinforces them by saying to continue with 'page' and to narrow 'query'. The remaining two parameters, page_size and asset_type, receive no explanation in either place, so the description only partially compensates for the coverage gap.

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?

States a specific verb (search) plus the exact match keys (ticker, name, or CNPJ) and the corpus (public asset classes), so the agent knows this is a lookup tool rather than a detail fetch. It does not name obm_get_asset as the follow-up for a single asset, so sibling differentiation is inferred rather than stated.

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?

Gives useful operational guidance: continue with 'page' and narrow 'query' when results are numerous. However, it never says when to prefer this over obm_get_asset or obm_list_assets, and there are no explicit when-not conditions, so routing must be guessed from tool names.

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