Skip to main content
Glama

aipricepatterns

by com.aipricepatterns
OverviewDiscussionsAdmin

Candle Market Snapshot

get_candle_market_snapshot
Read-onlyIdempotent

Return the full-OHLC candle context used by /candles: calibrated price/context/volume market memory for supported episodes, explicit rankingMethod and fallback reason, historical analogues, magnitude bands, versioned analogue ledger, freshness, and a signal-integrity gate. Similarity is not a directional probability. Analogues are dated look-alikes, not a tested rule; to backtest a rule built on the pattern (costs, walk-forward, Monte Carlo, an honest NO EDGE FOUND), use RLXBT MCP: https://rlxbt.com/docs/mcp?utm_source=aipricepatterns&utm_medium=referral&utm_campaign=ecosystem&utm_content=mcp_guide

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fNoForward horizon in bars. Only the chart presets 5, 10, 30, and 50 are supported
qNoCandles in the matched pattern. Only the chart presets 3, 5, 8, and 12 are supported
limitNoClosest analogues to list (1-20). Bands and direction always use the chart's 20 neighbours
symbolNoSupported chart symbol: BTCUSDT, ETHUSDT, or SOLUSDTBTCUSDT
anchorTsNoOptional historical replay anchor in Unix milliseconds. Omit for the latest chart candle
intervalNoSupported chart timeframe: 5m, 15m, 1h, 4h, or 1d5m
token_idNoOptional Chart access token (64-hex, same as X-Aipp-Chart / the token on /profile). After the daily free MCP quota, paid tools require the Chart $29/mo Stripe subscription. Legacy Manus token_id still works only when MCP_BILLING=manus.
chart_tokenNoOptional Chart access token. Prefer the X-Aipp-Chart header in the MCP client config so every tool call is covered.
includeAnalogueCandlesNoInclude OHLC arrays for every analogue and its continuation. False keeps the response agent-sized

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Number of closest candle analogues to return (1-20)"New value: +"Closest analogues to list (1-20). Bands and direction always use the chart's 20 neighbours"
  2. Changed2 schema fields changed
    • addedInput schema / properties / chart_token
      Added value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "anyOf": [
+    {
+      "not": {}
+    },
+    {
+      "minLength": 1,
+      "type": "string"
+    }
+  ],
+  "description": "Optional Chart access token. Prefer the X-Aipp-Chart header in the MCP client config so every tool call is covered."
+}
    • changedInput schema / properties / token_id / description
      Previous value: -"Optional Manus access token. Paid tools use tokenized service access, not a monthly subscription: when token_id is omitted the server returns payment_required with a Solana Pay invoice, and after payment you retry with the same token while the server uses Manus token/resolve to recover pending access."New value: +"Optional Chart access token (64-hex, same as X-Aipp-Chart / the token on /profile). After the daily free MCP quota, paid tools require the Chart $29/mo Stripe subscription. Legacy Manus token_id still works only when MCP_BILLING=manus."
  3. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the tool is known to be safe and idempotent. The description adds valuable behavioral caveats: 'Similarity is not a directional probability' and 'Analogues are dated look-alikes, not a tested rule' — these directly warn against misinterpretation. It also mentions 'signal-integrity gate' and 'freshness', providing behavioral context beyond the annotations. No contradiction.

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?

The description is dense but well-structured. It front-loads the main purpose and then lists the returned components. The inclusion of a URL with utm parameters is somewhat extraneous, but it serves as a pointer to an alternative for backtesting. Overall, every sentence contributes meaning, though it could be slightly more concise without losing key caveats.

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?

Given 9 parameters, no output schema, and no nested objects, the description is fairly complete. It lists all major output components (analogues, bands, ledger, freshness, integrity gate) and includes critical interpretive disclaimers. It doesn't specify the exact response format or data types, but since there is no output schema, this is an acceptable level of detail. It could mention pagination or limits, but the limit parameter is already in the schema. Overall, adequate for an agent to call and interpret results.

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 covers all 9 parameters with detailed descriptions (100% coverage), so the baseline is 3. The description does not add parameter-specific semantics beyond the schema; it focuses on the output content. It doesn't explain parameter relationships or syntax beyond what the schema provides, so it doesn't elevate the score.

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 the tool's purpose: 'Return the full-OHLC candle context used by /candles' and enumerates the specific components (calibrated price/context/volume market memory, rankingMethod, fallback reason, historical analogues, magnitude bands, versioned analogue ledger, freshness, signal-integrity gate). This is a specific verb+resource with a detailed list that distinguishes it from sibling tools like get_candle_analogue_map or get_candle_evidence_board, even though those are not named.

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?

The description provides a clear context for when to use the tool (for full candle context), but it does not explicitly state when to prefer this over sibling tools or when not to use it. It does point to an external tool (RLXBT MCP) for backtesting, which is a form of alternative guidance, but it lacks explicit comparisons to the listed sibling tools. Thus, it gives some context but no clear exclusions.

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

All aipricepatterns 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