Skip to main content
Glama

aipricepatterns

by com.aipricepatterns
OverviewDiscussionsAdmin

Candle Track Record

get_candle_track_record
Read-onlyIdempotent

Walk forward the exact chart candle configuration (symbol, interval, q, f) over independent resolved anchors. Compares analogue and volatility-scaled range bands against the unconditional baseline with coverage, confidence intervals, Winkler scores, regime diagnostics, and explicit non-directional signal integrity.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fNoExact forward horizon to evaluate: 5, 10, 30, or 50 bars
qNoExact chart pattern length to evaluate: 3, 5, 8, or 12 candles
endTsNoOptional Unix-millisecond cutoff that pins the evaluation dataset for reproducibility
symbolNoSupported chart symbol: BTCUSDT, ETHUSDT, or SOLUSDTBTCUSDT
anchorsNoIndependent resolved anchors to evaluate, spaced f bars apart (10-120). Default 120 matches /candles; fewer is faster but noisier
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.
analogueLimitNoNearest analogues used at every walk-forward anchor (5-200). Default 20 matches /candles
includePointsNoInclude every resolved walk-forward anchor. False returns an agent-sized summary

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. Changed4 schema fields changed
    • changedInput schema / properties / analogueLimit / default
      Previous value: -50New value: +20
    • changedInput schema / properties / analogueLimit / description
      Previous value: -"Nearest analogues used at every walk-forward anchor (5-200)"New value: +"Nearest analogues used at every walk-forward anchor (5-200). Default 20 matches /candles"
    • changedInput schema / properties / anchors / default
      Previous value: -40New value: +120
    • changedInput schema / properties / anchors / description
      Previous value: -"Independent resolved anchors to evaluate. Anchors are spaced f bars apart (10-120)"New value: +"Independent resolved anchors to evaluate, spaced f bars apart (10-120). Default 120 matches /candles; fewer is faster but noisier"
  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

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds real behavioral value by disclosing what the evaluation produces (coverage, confidence intervals, Winkler scores, regime diagnostics, non-directional signal integrity) and the walk-forward/independent-anchor method, which matters since there is no output schema.

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?

Two tightly packed sentences with the action front-loaded and no filler. The phrase 'explicit non-directional signal integrity' is somewhat opaque jargon, slightly hurting readability, but the definition is appropriately sized.

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?

For a 10-parameter evaluation tool with no required params and no output schema, the description explains the method and the metrics returned, compensating for the missing output schema. Its main shortfall is routing guidance relative to the many sibling candle tools, but the core operation and results are covered.

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%, so all ten parameters are already documented at the schema level, making 3 the baseline. The description echoes the four configuration parameters (symbol, interval, q, f) but adds no syntax or constraint detail beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: walk forward the exact candle configuration (symbol, interval, q, f) over resolved anchors, and names what it compares (analogue vs volatility-scaled bands against baseline). This is clearly a walk-forward track-record evaluation, distinguishable from siblings like the analogue map or evidence board. It does not explicitly name or contrast a sibling, keeping it at 4.

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 by the framing (evaluate a configuration's historical track record across independent anchors), but there is no explicit when-to-use, when-not-to-use, or alternative tool named among the many candle siblings. Costs/performance tradeoffs are only hinted at in the anchors parameter description, not here.

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