Skip to main content
Glama

OBM - Open Brazil Market

Situação e fontes dos dados

obm_get_data_status
Read-onlyIdempotent

Datas de referência por dataset, catálogo de fontes ou, com chave, plano e cota restante. Status é isento de cota como na API REST.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "obm_get_data_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewNostatus: datas por dataset (sem cota); sources: fontes; account: plano e cota restante (exige chave).status

Output Schema

NameRequiredDescriptionDefault
dataYes
metaYes
sourceYes
reference_dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 genuinely new behavior beyond them: the status view does not consume quota (and this mirrors REST API semantics), and the account view requires an API key. It stops short of describing error behavior when the key is absent.

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 sentences, no filler, and the primary (quota-free) case is stated first. The telegraphic style and awkward ordering of 'ou, com chave,' cost a little readability but nothing is wasted.

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?

An output schema exists, so the description need not explain return shapes, and it correctly focuses on view selection plus the auth/quota caveats. For a single optional enum parameter and a read-only metadata tool this is close to sufficient, with only key-missing behavior left implicit.

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 100%, so the enum meanings are already fully documented in the input schema, and the description largely restates them ('datas por dataset', 'fontes', 'plano e cota restante'). The only added meaning is the quota exemption tied to the status view, which is a marginal delta over structured data.

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 enumerates the three concrete payloads the tool exposes: reference dates per dataset, the source catalog, and (with a key) plan plus remaining quota. That is specific enough for an agent to know what comes back, though it is a noun-phrase fragment with no explicit verb and it never contrasts itself with siblings like obm_get_asset or obm_get_financials.

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?

Usage is only implied: the reader must infer that 'status' is the cheap default view and 'account' is the one needing credentials. There is no explicit when-to-use/when-not guidance and no named alternative, so routing between views is left to the enum in the schema rather than to the prose.

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