Skip to main content
Glama

aipricepatterns

by com.aipricepatterns
OverviewDiscussionsAdmin

Explain Candle Match

explain_candle_match
Read-onlyIdempotent

Why this twin ranked under the reported method: distance, anatomy-token observations, and outcome vs neighbour p10/p50/p90. Shape tokens alone cannot explain a context/volume score. Similarity is not P(direction).

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
rankNo1-based rank in the selected retrieval method's neighbour list (1 = closest).
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.
analogueAnchorTsNoTwin episode to open, Unix ms. If omitted, use rank.
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. Changed1 schema field changed
    • changedInput schema / properties / rank / description
      Previous value: -"1-based rank in the overlay-v1 neighbour list (1 = closest)."New value: +"1-based rank in the selected retrieval method's neighbour list (1 = closest)."
  4. 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."
  5. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful epistemic context that annotations cannot: 'Similarity is not P(direction)', warning the agent not to over-interpret the ranking. It does not disclose response shape or size, but with annotations carrying safety this is adequate.

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 compact and front-loads the 'Why' framing before the supporting detail. Every clause carries content, though the middle clause is dense with unglossed jargon. No filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 11-parameter tool with no output schema, the description only gestures at the return content (distance, anatomy-token observations, outcome vs p10/p50/p90) without explaining structure, and gives no guidance on how rank and analogueAnchorTs interact. It is minimally adequate but leaves clear gaps for a tool of this complexity.

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 all 11 parameters (including enum presets for f, q, symbol, interval) are documented in the schema itself. The description mentions 'distance', 'anatomy-token observations', and 'p10/p50/p90' but these describe outputs, not the parameters, so it adds little beyond the schema. Baseline 3 applies.

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

Purpose3/5

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

The description does state a purpose: explaining why a matched 'twin' ranked as it did, listing the factors (distance, anatomy-token observations, outcome vs neighbour p10/p50/p90). However, it leans heavily on unexplained domain jargon ('twin', 'anatomy-token', 'context/volume score') and never distinguishes itself from close siblings like inspect_candle_analogue or get_candle_analogue_map. The core verb+resource is present but the scope boundaries are vague.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no named alternative among the many candle siblings. The caveat 'Shape tokens alone cannot explain a context/volume score' is an interpretive note rather than a routing instruction, leaving the agent to infer when this tool is appropriate.

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