Skip to main content
Glama

Near-live price bars

price_candles
Read-onlyIdempotent

Near-live price bars (OHLCV) for a pair: interval "1h" (default) or "1d", oldest first, each bar { t, o, h, l, c, v }. This is the lane a bot reads to compute its OWN indicators (moving averages, momentum, whatever it wants), so CoinLobster does not need to ship them. NEAR-LIVE and separate on purpose from market_history, which is the daily archive that settles days behind: every reply carries newest_candle_age_min and stale so a live lane is never confused with a stopped one. Keyless covers the free pairs up to 168 bars; a paid plan covers every streamed pair up to 720 bars (asking for more returns the cap and says so in capped). The newest bar is still forming. 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. Keyless calls reach the free pairs only; a paid plan reaches every streamed pair. A pair this server does not stream comes back covered:false.
limitNoHow many bars, newest-ending. Capped at 168 keyless and 720 on a paid plan; asking for more returns the cap, and the payload says so in `capped`.
intervalNoBar length: "1h" (default) or "1d". Anything else is read as 1h.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNoOne line saying what the numbers cover, or why there are none. Read it before reporting any zero as a market reading.
pairNoThe pair these candles are for.
as_ofNoThe time of the newest bar, in milliseconds.
countNoHow many rows this reply carries.
staleNoTrue only when the newest bar is older than a live lane explains. When true the numbers are stopped, not the current price.
cappedNoPresent only when an argument was cut down to a ceiling. Absent means nothing was clamped, so a smaller number than you asked for is the data and not a limit.
candlesNoThe bars, oldest first, each { t, o, h, l, c, v }: time, open, high, low, close and volume. The newest bar is still forming. This is the NEAR-LIVE lane, not the days-behind daily archive that market_history reads.
coveredNoFalse when this server does not stream the pair at all. No plan adds it.
intervalNo1h or 1d. The bar length each candle covers.
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.
free_pairsNoThe pairs a keyless connection can read, returned when the pair asked for is not one of them.
stale_noteNoPresent when stale is true: how far past live the newest bar has fallen.
access_noteNoWhat this connection could not return and what lifts it. Always pass this on to the user: it is the only place that information appears.
newest_candle_age_minNoHow many minutes old the newest bar is, so a live lane can be told from a stopped one.

TDQS

A4.7/5.0
Behavior5/5

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

The description discloses staleness fields (newest_candle_age_min, stale), the plan-based caps (168 vs 720), the capped field, the fact that the newest bar is still forming, and that it is descriptive data only. This goes well beyond the annotations and accurately reflects the operational behavior.

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?

The description is dense but every clause addes value: resource, interval, format, ordering, intended use, distinction from sibling, staleness fields, plan caps, and data-only nature. No waste and front-loaded with the core purpose.

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?

Combined with the rich schema and output schema, the description covers defaults, caps, error responses (capped/covered), freshness, ordering, and the live-vs-archive distinction. An agent has everything needed to invoke this tool correctly and interpret its role.

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?

The input schema already documents all four parameters with 100% coverage, including defaults, plan caps, and invalid-interval fallback. The description restates those limits and defaults rather than adding new parameter-level meaning, though it does add context about bar ordering and OHLCV structure.

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?

The description clearly states a specific resource (OHLCV price candes) and the action (retrieving near-live bars). It dintinguishes itself from market_history by emphasizing it is the live, bot-facing lane, so an agent can select it without opening sibling schemas.

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?

It expliciitly says this tool is for a bot computing its OWN indicators and separately on purpose from market_history, which settles days behind. This gives clear when-to-use guidance and names the alternative to avoid confusion.

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