Skip to main content
Glama

aipricepatterns

by com.aipricepatterns
OverviewDiscussionsAdmin

What Is Odd in Candle Memory

what_is_odd_in_candle_memory
Read-onlyIdempotent

Explain what stands out in the retrieved evidence: terminal-outcome band versus all-history, observed coverage, closest episode versus median, era clustering and neighbour distances. Suggests a concrete level hypothesis to investigate next; execution eligibility is reported separately.

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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds one genuinely useful boundary: 'execution eligibility is reported separately,' clarifying what this tool does NOT return. Beyond that it says nothing about return format or limits, so with annotations carrying the safety burden a 3 is appropriate.

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 sentences with no filler; the enumerated facets are front-loaded and the closing clause about execution eligibility is placed where it matters. It is dense with domain jargon but not padded.

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?

With 9 parameters and no output schema, the description should carry more of the return-shape burden. It does list the analytical facets, which helps, but undefined terms ('terminal-outcome band', 'era clustering') and the lack of any structural sense of the response leave the agent under-informed about what it will receive.

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 schema already documents all nine parameters (horizons, pattern lengths, limits, symbol, anchor, interval, tokens, candle flag). The description references 'observed coverage' and 'closest episode' loosely but adds no syntax or format meaning beyond the schema. Baseline 3 is correct when the schema does the heavy lifting.

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?

The description states a specific analytical verb+resource: it explains what standouts exist in retrieved evidence, enumerating concrete facets (terminal-outcome band vs all-history, coverage, closest episode vs median, era clustering, neighbour distances). It is clear what the tool does, but it never differentiates itself from close siblings like explain_candle_match, get_candle_evidence_board, or evaluate_candle_hypothesis.

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?

No explicit when-to-use or when-not-to-use guidance is given, and no sibling alternative is named. The phrase 'Suggests a concrete level hypothesis to investigate next' loosely implies a handoff to evaluate_candle_hypothesis, but the agent must infer this rather than being told.

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