Skip to main content
Glama
Sign In

qmax

by io.github.profitphil
OverviewDiscussionsAdmin

Price over time (line)

qmax_get_price_history
Read-onlyIdempotent

The asset's price over time as points (ms timestamp, price in QU, and for recently recorded points the best bid, ask and pool price). Points before 'recordedSince' were rebuilt from past trades as hourly volume-weighted averages (marked src 'trades'); after it QMax recorded the price about every 10 minutes. OHLC and volume are in qmax_get_candles.

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_price_history"
  }
}

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

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.3/5.0
Behavior5/5

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

Annotations cover read-only/idempotent safety, and the description adds substantial behavior beyond them: the recording cadence (~every 10 minutes after 'recordedSince'), the reconstruction of earlier points as hourly VWAP marked src 'trades', and the composition of each point. With no output schema, this return-format disclosure is exactly what 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.

Conciseness4/5

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

Purpose is front-loaded in the first clause, and the sibling routing lands cleanly at the end. It is dense with parenthetical detail but every sentence carries information, with no filler.

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?

With no output schema, the description does the heavy lifting for return values and does it well, covering timestamps, price units, bid/ask/pool fields, the src marker, and the recording cadence. Minor omissions (array framing, ordering) are not enough to undermine an otherwise complete picture for a two-parameter read tool.

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 coverage is 100%, so both parameters are already fully documented with examples and defaults. The description mentions return-side concepts like 'recordedSince' but adds little syntax or meaning for the 'asset' and 'range' inputs beyond what the schema provides, so the baseline 3 holds.

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 specific resource (the asset's price over time) and the exact shape of the returned data (ms timestamp, price in QU, bid/ask/pool price). It explicitly names the sibling it is not, noting 'OHLC and volume are in qmax_get_candles', so an agent can separate this from the candles tool without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides clear routing context by telling the agent that OHLC and volume live in qmax_get_candles, implying this tool is for line/point price series instead. It lacks an explicit 'use this when' statement or exclusion list, but the sibling reference gives usable direction.

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