Skip to main content
Glama

aipricepatterns

by com.aipricepatterns
OverviewDiscussionsAdmin

Inspect Candle Analogue

inspect_candle_analogue
Read-onlyIdempotent

Open one neighbour from the reported rankingMethod as an episode: query OHLC, twin OHLC, rebased forward, distance, display similarity, dated permalinks. Not a directional call.

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 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.
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. 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. 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)."
  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 declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false, so the description does not need to re-establish safety. It adds useful behavioral context by clarifying that the tool is not a directional call and by enumerating exactly what the inspection returns, which helps the agent anticipate the response shape.

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 a single dense sentence with a front-loaded action and a colon-delimited list of delivered components. Every clause adds information and there is no filler, though the long list requires careful parsing.

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 read-only inspection tool with no output schema, the description lists the key returned components and frames the operation clearly. Parameters and safety are already fully covered by the schema and annotations; the main remaining gap is explicit sibling routing, which is more of a usage-guideline concern.

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 every one of the 11 parameters already has explicit enums, defaults, constraints, and descriptions. The main description does not add parameter-level semantics beyond tying the tool to a 'reported rankingMethod,' so the baseline 3 is appropriate.

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 states a specific action ('Open one neighbour from the reported rankingMethod as an episode') with a clear resource and output scope: OHLC, twin OHLC, rebased forward, distance, display similarity, and dated permalinks. The closing 'Not a directional call' distinguishes it from directional/decision siblings, and the 'reported rankingMethod' hook differentiates it from map-level or evidence-board tools.

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?

The description clearly implies when to use it: after a ranking method has reported a neighbour list, to inspect one specific neighbour. It also gives an explicit when-not ('Not a directional call'). It does not name alternative sibling tools such as explain_candle_match or get_candle_evidence_board, so it stops just short of full routing guidance.

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