Skip to main content
Glama

aipricepatterns

by com.aipricepatterns
OverviewDiscussionsAdmin

Candle Market Snapshot

get_candle_market_snapshot
Read-onlyIdempotent

Find dated historical situations comparable to the current BTC, ETH or SOL window and see what followed. Returns chart-parity OHLC, rankingMethod and fallback reason, historical terminal-close quantiles, range ledger and freshness. Use evaluate_candle_hypothesis to test a specific level and get_candle_track_record to check range quality. 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 token. No token or payment is needed during the free access experiment.
chart_tokenNoOptional account key; all tools work anonymously during the free access experiment.
includeAnalogueCandlesNoInclude OHLC arrays for every analogue and its continuation. False keeps the response agent-sized

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / chart_token / description
      Previous value: -"Optional Chart access token. Prefer the X-Aipp-Chart header in the MCP client config so every tool call is covered."New value: +"Optional account key; all tools work anonymously during the free access experiment."
    • changedInput schema / properties / token_id / description
      Previous 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."New value: +"Optional token. No token or payment is needed during the free access experiment."
  2. 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"
  3. 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."
  4. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds real value beyond them: it enumerates returned artifacts (chart-parity OHLC, rankingMethod, fallback reason, terminal-close quantiles, range ledger, freshness) and flags the key epistemic limit 'Similarity is not a directional probability' plus 'analogues are dated look-alikes, not a tested rule'. It does not discuss rate limits or failure modes for the fallback path.

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?

Front-loaded with the purpose sentence, then return contents, then sibling routing and caveats. Nearly every sentence carries information, though the final promotional link with full UTM parameters is extraneous marketing that dilutes an otherwise tight definition.

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 must carry the return-value burden and largely does, naming the key response fields and the fallback indicator. Nine optional parameters are fully documented in the schema, and sibling routing plus epistemic caveats are present; only the meaning of items like 'range ledger' and 'freshness' is left unelaborated.

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% and every parameter (including the f/q presets, limit vs chart's 20 neighbours, anchorTs replay, and the optional tokens) is documented in the schema itself. The description adds no syntax, default, or format detail beyond what the schema already provides, so the baseline 3 applies.

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 verb and resource: find dated historical analogues to the current BTC/ETH/SOL window and see what followed. It also names sibling tools (evaluate_candle_hypothesis, get_candle_track_record), so an agent can distinguish this analogue-search tool from the hypothesis-testing and track-record tools without opening any 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?

Explicitly routes to alternatives with conditions: evaluate_candle_hypothesis 'to test a specific level' and get_candle_track_record 'to check range quality', plus a pointer to an external backtesting service for rule testing. Clear context for choosing between siblings, but there is no explicit statement of when this tool should NOT be used.

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