Skip to main content
Glama

AINDEX

Markets at a glance, across venues

market_brief
Read-only

For up to eight markets, one compact read each, with ready-to-read lines: 1h and 4h trend (with what points against it), RSI, ATR and its percentile, volume against its average, RSI divergence, the nearest support and resistance in ATRs; funding with its 7-day percentile and change; open interest change (Lighter on Robinhood Chain and Binance); Binance order flow (taker buys, CVD, long/short accounts, top traders); the same market on Lighter, Hyperliquid (with its xyz stock perps), Binance and Bybit with funding and price gaps; and the liquidation map (TrueNorth, labelled).

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": {
      "symbols": "<symbols>"
    },
    "name": "market_brief"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds real value by disclosing the data provenance — Lighter on Robinhood Chain and Binance, Hyperliquid xyz stock perps, TrueNorth liquidation map — which signals an expensive multi-venue aggregation. It does not warn about latency, rate limits, partial-venue failure, or what happens if a symbol is unsupported on one of the listed venues.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The scope constraint is correctly front-loaded in the first clause, which is the right structure. But the remainder is a single semicolon-chained inventory of roughly a dozen metrics that reads as a data dictionary rather than guidance, making it hard to scan. Roughly half of that enumeration could be compressed or dropped without losing decision-relevant information.

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 no output schema, the description does the necessary work of enumerating what comes back, which is appropriate for a rich aggregate read. What is missing is proportionate to the tool's complexity: an aggregation across four-plus venues with no note on cost, latency, or degradation when a venue lacks the market. Symbol format and the choice against sibling market tools are also unaddressed.

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 0%, so the description must carry the parameter burden. It does clarify that symbols is a list of markets capped at eight, which is meaningful semantics beyond the bare array type. However, the schema pattern permits characters like ':', '/', '=', '^' that imply venue-qualified or contract-style identifiers, and the description never explains the accepted symbol format, so an agent could easily pass 'BTC' when 'BTCUSDT' or 'venue:BTC' is expected.

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 opens with a concrete scope statement — 'For up to eight markets, one compact read each' — which tells an agent this is a batched multi-market snapshot rather than a single-market lookup. The enumerated payload (trend, RSI, ATR, funding, OI, order flow, cross-venue comparison, liquidation map) makes the resource specific. It never names a sibling (market_dossier, market_overview, market_screener, market_today) to distinguish itself, so an agent must guess which market tool to pick.

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?

There is no when-to-use guidance, no stated prerequisites, and no alternatives named despite several overlapping siblings in the catalog. The only implied constraint is the eight-market cap, which is already enforced by the schema's maxItems. Nothing tells an agent when this is preferable to a single-market tool or a screener.

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