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 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.
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. 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"
  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/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety. The description adds meaningful process/output context: it walks forward over independent anchors, compares range bands against an unconditional baseline, and returns coverage, confidence intervals, Winkler scores, regime diagnostics, and non-directional signal integrity. This goes beyond the annotations without contradicting them.

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?

Two dense sentences carry the full purpose and output scope with no filler. The core action is front-loaded, and the metric enumeration earns its place by explaining what the agent will receive, especially since there is no output schema.

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 complex statistical tool with 10 parameters and no output schema, the description lists the key return concepts (coverage, confidence intervals, Winkler scores, regime diagnostics, signal integrity), which is sufficient for selection. However, it leaves terms like 'independent resolved anchors' and the exact walk-forward procedure somewhat underspecified, which may matter for invocation.

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 the baseline is 3. The description references symbol, interval, q, and f as the configuration, and mentions anchors implicitly, but it does not add any parameter meaning beyond what the schema already provides. It neither compensates nor detracts.

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 names a specific verb ('Walk forward') and resource ('exact chart candle configuration (symbol, interval, q, f) over independent resolved anchors'), and it distinguishes this tool from siblings by focusing on statistical track-record evaluation with coverage, Winkler scores, and non-directional signal integrity. This is clearly a backtest/validation tool, not just another candle data or analogue lookup.

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 implies the tool is for evaluating the performance of a specific candle configuration over resolved anchors, but it never explicitly states when to use this tool versus alternatives like get_candle_analogue_map or inspect_candle_analogue. There are no exclusions or routing hints, so the agent must infer usage from context.

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