Skip to main content
Glama

One-call market brief

market_brief
Read-onlyIdempotent

A complete current market brief for ONE coin in a single call: price, cross-venue funding with carry, open interest, whale flow versus the coin's own baseline, recent liquidations and historical context. The plain-English name for trade_context (identical data and credit cost). Use for a general "what is happening with BTC / how is ETH positioned" question, and do not also call the separate whale, funding or liquidation tools unless the user drills into one of them. Descriptive market data only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
coinNoAlias for pair.
pairNoTrading pair, for example ETH/USD. A bare symbol like ETH is read as ETH/USD. Defaults to BTC/USD when omitted. Any streamed pair answers keyless; off the free pairs a keyless reply is the lite shape and names what it withheld in locked_layers.
compactNoReturn one line of plain text rather than the JSON blob, about 30 tokens instead of 800. Same facts, same windows, same dates, no structured fields to read. Defaults to false.
position_usdNoPosition size in US dollars, for example 25000. Above zero only. When given, carry_cost adds per_day_usd_at_current_rate, the dollars a day the current funding average across exchanges works out to at that size. Arithmetic on the rate as it stands now, not a projection of future rates. Omit and carry_cost still carries the percentage and APR figures.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
lineNoThe composed one-line answer, returned only when compact:true was asked for. The same facts, the same windows and the same dates as the full shape.
noteNoOne line saying what the numbers cover, or why there are none. Read it before reporting any zero as a market reading.
pairNoThe pair this context describes.
depthNoWhich shape came back: lite, free-pair or keyed.
priceNoLast traded price.
compactNoPresent and true only on a compact:true call, where the whole answer is the single line in `line`.
fundingNoaverage_rate across exchanges, how many exchanges are in it, the interval in hours, and minutes to the next funding time.
crowdingNoThe crowding read and the overexposed side. Null without a paid plan.
availableNoFalse when this lane could not answer: a producer is dark, the pair sits outside this plan, or the argument named something we do not carry. Absent or true means the numbers are a real reading, not a guess.
stats_24hNoThe 24h statistics block. Absent on the lite shape, where locked_layers names it.
carry_costNoArithmetic on the current funding average: percent per day, the same as an annual rate, which side pays, and dollars a day when position_usd was passed. Not a projection of future rates.
whale_flowNoWhale direction against the same coin logged baseline: the multiple, days logged, record and N-day-high flags, and buy share now versus 7 days. Dollar sizes are added on a paid plan.
price_readsNoPlain descriptions of price against its own recent hours, computed from hourly candles: vs_recent_average (above or below its 50-hour and 200-hour average, and which way it is drifting), recent_move (how stretched the latest move is, plus the change against 7 days ago) and choppiness (calm, normal or choppy). Each block is available:true with values or available:false with a plain reason; a leg with too few recorded hours is null with a note, never a made-up neutral. Descriptive, not a trade signal.
locked_layersNoNamed rather than silently missing: which blocks this connection did not receive.
vs_own_historyNoWhere funding and open interest sit against the same pair recorded days: phrase, band, day count, the date the reading is from, and how past cases resolved.
open_interest_usdNoOpen interest in dollars across the exchanges that publish it.
liquidations_recentNoForced closes visible right now: count, long_usd, short_usd and window_minutes. A timing series, market-wide totals run higher.

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already provide readOnly, idempotent, and non-destructive hints; the description adds that the tool is descriptive only, that data and credit cost are identical to trade_context, and that it is a one-call aggregation. These are meaningful behavioral clarifications beyond the annotation booleans.

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

Conciseness5/5

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

Three sentences with no filler: the payload is front-loaded in sentence one, the sibling-alias and credit note in sentence two, and usage/exclusion guidance in sentence three. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the rich output schema and detailed input schema, the description covers scope, alias, credit cost, exclusions, and use case. Nothing needed to choose or invoke the tool correctly is missing.

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 schema already documents coin, pair, and position_usd. The description reinforces the 'ONE coin' scope but does not need to add parameter-level detail; baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description states exactly what it returns ('complete current market brief for ONE coin in a single call') and enumerates the data categories: price, funding with carry, open interest, whale flow, liquidations, historical context. It also differentiates from the identical trade_context sibling and from granular whale/funding/liquidation tools.

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?

Gives explicit when-to-use framing ('general what is happening with BTC / how is ETH positioned question') and explicit when-not-to: do not also call separate whale, funding, or liquidation tools unless the user drills in. This is exactly the routing guidance an agent needs.

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.

TDQS

A3.8/5.0
Disambiguation2/5

The set contains at least five exact alias pairs (coin_liquidations/liquidations, market_brief/trade_context, flag_outcomes/signal_outcomes, whal_activity/whale_profile, whal_tape/whale_trades) plus many near-synonymous market_, whal_, hl_, and liquidation tools. The descriptions are excellent and cross-reference each other, but the sheer density of overlapping names makes tool selection genuinely difficult for an agent.

Naming Consistency4/5

Names are uniformly snake_case and largely follow a domain-prefix + noun convention (market_*, whale_*, hl_*, defi_*). Minor deviations exist: standalone liquidations, my_access, and duplicate aliases with different names, but the overall style is predictable and not mixed.

Tool Count2/5

38 tools is well past the 25+ threshold for a heavy toolset, and roughly ten of them are redundant alias pairs that could be collapsed into five. While the domain is broad, many one-call briefs and whale-flow variants overlap enough that the count feels inflated rather than justified.

Completeness4/5

The surface is remarkably broad for a read-only data server: price, funding, open interest, liquidations, whale flows, DeFi, options, news, signals, and access controls are all covered. Minor gaps remain, such as no explicit supported-pairs listing and some paid-tier caps that can surprise agents, but these are workaroundable.

Resources