Skip to main content
Glama
Sign In

qmax

by io.github.profitphil
OverviewDiscussionsAdmin

Candles and volume from real trades

qmax_get_candles
Read-onlyIdempotent

Open, high, low, close, QU volume, units and trade count per candle, built from every trade QX and QSwap logged (a minute wide at the finest; about six months back, which is all the Qubic archive has: its trade records begin in April 2026). A candle exists only where something traded, so a gap means no trades. The response also gives the last 24 hours of volume across both markets.

Returns: { asset, range, interval, venue, candles: [{ t (ms), o, h, l, c, volumeQu, volumeQty, trades }], truncated?, available?, volume24hQu, trades24h }. Prices are QU per unit.

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": {
      "asset": "<asset>"
    },
    "name": "qmax_get_candles"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetYesAsset symbol, for example CFB or QDOGE (case does not matter). qmax_list_assets lists the tradable symbols.
rangeNoHow far back to look. 'all' is everything QMax has (about six months).7d
venueNoWhich market's prices: QX (order book), QSwap (pool), 'all' (treat both as one market), or 'auto' (the market the live price comes from).auto
intervalNoCandle width: a minute up to a day (default suits the range). One answer holds at most the latest 5,000 candles

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / asset / description
      Previous value: -"Asset symbol, for example CFB or QDOGE (case does not matter). Use qmax_list_assets to find one."New value: +"Asset symbol, for example CFB or QDOGE (case does not matter). qmax_list_assets lists the tradable symbols."
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the bar is lower — yet the description adds real behavioral context: candles exist only where trading occurred, the archive starts April 2026, the finest granularity is one minute, and a 24h cross-venue volume summary is included. These are non-obvious data-shape facts an agent needs.

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?

Front-loaded with what the tool produces, followed by caveats and then an explicit return shape. Every sentence carries information (semantics, limits, or structure) with no filler or repetition.

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?

With no output schema, the description carries the return-value burden and does so fully, listing every field of the candle object and the top-level fields. Combined with the data-limit caveats, an agent has everything needed to call and interpret this tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds the crucial unit semantics the schema omits — prices are QU per unit — plus the relationship between range and the ~6-month archive. It does not re-explain the enum choices the schema already documents.

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?

States a precise verb and resource — OHLC, volume, unit and trade-count candles — and pins down the source: built from every trade logged by QX and QSwap. That sourcing detail implicitly separates it from sibling price/tape tools like qmax_get_price_history and qmax_get_tape.

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 implied rather than routed: it notes that gaps mean no trades and that history spans roughly six months, which helps an agent reason about results, but it never says when to prefer this over qmax_get_price_history, qmax_get_tape or qmax_get_flow. No explicit alternatives or exclusions are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All qmax toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources