Skip to main content
Glama

decker.get_episodes

Price-axis EPISODE history — answers 'where did I buy/sell last time, what was the target value and the event chain then, and where did price move WITHOUT a signal (and which target values it passed = missing points)'. Read-only from the persisted event ledger (no recompute). episodes (newest first) = one target selection until the next: target {price, from_price, reason}, chain (primary-unit judgment events), signals {ts, side, entry, targets, resolved{status, close, bar_low, bar_high}}, left (unit ends in that episode: result CONFIRMED | FAILED | MISSING = a target price passed before its judgment bar | EXPIRED = judgment sequence lapsed), missing, signal_gap (no signal in that episode), move {start_close, end_close, pct}. signal_gaps (ascending) = the interval between consecutive signals with its price move and the missing points inside (last one is open). Unit ends carry side (up/down = the target's run direction), cand and reason — classify on the read side; do not re-decide coordinates. History starts at the first persisted event of this generation.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>",
      "timeframe": "<timeframe>"
    },
    "name": "decker.get_episodes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNonumber of episodes
symbolYese.g. BTCUSDT
timeframeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it declares read-only, no recompute from the persisted event ledger, ordering (newest first for episodes, ascending for signal_gaps), the boundary 'history starts at the first persisted event of this generation', and an explicit instruction not to re-decide coordinates on read. It omits auth, rate limits, and pagination/truncation behavior for limit.

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?

Purpose is front-loaded in the first clause, and the rest is dense but productive field-level documentation. Given no output schema exists, the enumeration of episode fields earns its space, though the sentence is long and could be split for scanability.

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?

There is no output schema, so the description compensates by defining the returned structures, unit-end statuses (CONFIRMED/FAILED/MISSING/EXPIRED), and ordering conventions. What remains thin is input-side guidance — how timeframe and limit shape the result set — and any statement of failure modes for an invalid symbol.

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 coverage is 67% and the description adds essentially nothing about the three input parameters — symbol, timeframe, and limit are left entirely to the schema. The detailed prose is about return structure (`episodes`, `signal_gaps`, unit-end statuses), not about parameter meaning, so the baseline 3 applies.

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 names a specific resource — price-axis episode history — and frames it with concrete questions it answers (last buy/sell, target value and event chain, price moves without a signal). It implicitly separates itself from signal-listing siblings by emphasizing 'WITHOUT a signal' and 'missing points', though it never names a sibling tool directly.

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 conveyed through the framing questions ('where did I buy/sell last time...'), which implies this is the reconstruction/history tool rather than a live-state tool. There is no explicit when-not guidance or named alternative (e.g. get_signals vs get_trigger_history) to route an agent deciding between them.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.