Skip to main content
Glama
trading-crew-mcp

trading-crew-mcp

suggest_chain

Finds a connected chain of swing points that no candle cuts through on the chart's current timeframe and returns points to pass to draw_chain.

Instructions

Find a connected chain of swing points that no candle cuts through, on the chart's current timeframe. side "above" = falling chain over highs (red), "below" = rising chain under lows (green). Returns points to pass straight to draw_chain, with the same tolerance.

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": {
      "side": "<side>"
    },
    "name": "suggest_chain"
  }
}

Input Schema

NameRequiredDescriptionDefault
sideYes
countNo
strengthNo
toleranceNo
max_pointsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose useful behavior: the result is timeframe-dependent, the chain is defined by a geometric constraint (no candle cuts through), and tolerance semantics match draw_chain. It says nothing about what happens when no valid chain exists, cost/performance, or whether the operation is purely read-only - gaps that matter for an unannotated tool.

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?

Three tight sentences with the core definition front-loaded, followed by enum semantics and the output hand-off. No filler, though 'with the same tolerance' is slightly cryptic without knowing draw_chain's contract.

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

Completeness2/5

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

This is a moderately complex analytical tool - five parameters, zero schema descriptions, no annotations, no output schema - and the description documents only one and a half of those parameters. An agent could call it with the required 'side' but would be guessing at how count, strength, and max_points shape the result or what the returned points look like.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across five parameters, and the description explains only 'side' (above = falling chain over highs, below = rising chain under lows) and touches 'tolerance' via the draw_chain reference. The four optional parameters - count (50-500), strength (2-10), max_points (2-8), tolerance (0-2) - get no meaning at all, and count versus max_points in particular is unresolvable from the name alone.

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 concrete verb and resource - 'Find a connected chain of swing points that no candle cuts through' - scoped to the chart's current timeframe. It implicitly separates itself from draw_chain by framing its output as input for that sibling, though it does not distinguish itself from find_pivots, which an agent could easily confuse it with.

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?

It establishes the operating context (current timeframe) and gives a downstream hand-off hint ('points to pass straight to draw_chain'), which implies this is the analysis step before drawing. However, there is no explicit when-to-use versus find_pivots or draw_trend_line, and no stated preconditions or failure cases.

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