Skip to main content
Glama
trading-crew-mcp

trading-crew-mcp

draw_chain

Draw connected chains through pivot points above swing highs or below swing lows on TradingView charts, with candle-cut validation unless forced.

Instructions

Draw a connected chain of straight lines through pivot points (each line starts where the last ended). side "above" = red chain over swing highs, "below" = green chain under swing lows. Refuses and reports the candles if any line would cut through a candle, unless force is true.

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

Input Schema

NameRequiredDescriptionDefault
sideYes
colorNo
forceNo
widthNo
pointsYes
toleranceNoPoints a candle may overshoot a line before it counts as cutting it (default 0)
extend_rightNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, this description carries the full burden and does volunteer a genuinely important behavior: the tool refuses and reports offending candles if a line would cut through one, unless force is true. That is exactly the kind of validation detail an agent needs before calling. It still omits what happens to existing drawings and what a successful call returns (e.g. a drawing id), so it is not fully transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, all load-bearing: identity and chaining first, side semantics second, then the failure mode with its escape hatch. No filler, and the most important constraint is stated before the agent commits to a call.

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 a 7-parameter mutation tool with no annotations and no output schema, a few gaps remain: the return value is never described, the effect on existing drawings is unstated, and three parameters (width, extend_right, color-vs-side) get no meaning at all. The core drawing and refusal behavior is well covered, making it adequate but not complete.

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

Parameters4/5

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

Schema description coverage is only 14%, so the description has to compensate, and it does for the highest-risk parameters: side is given concrete visual semantics including implied color, force is explained as the override for the candle-cut-through refusal, and points is anchored to pivot points. It leaves width, extend_right, and color's interaction with side unexplained, and points still lacks structure detail (the schema covers time/price).

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?

Names a specific verb and resource — 'draw a connected chain of straight lines through pivot points' — and clarifies the chaining semantics with '(each line starts where the last ended)', which separates it from a single-segment tool like draw_trend_line. It does not explicitly contrast itself with the suggest_chain sibling, so the differentiation is implied rather than stated.

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?

The side definition ('above' = red chain over swing highs, 'below' = green chain under swing lows) gives a usable trigger condition, so an agent can infer when to use it. However, it never states prerequisites (e.g. needing pivot points from find_pivots), when not to use it, or why to choose drawing over suggest_chain.

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