Skip to main content
Glama
trading-crew-mcp

trading-crew-mcp

draw_trend_line

Draw a straight trend line between two exact candle time and price points on a TradingView chart, with optional color, width, and right extension.

Instructions

Draw a straight line between two points (exact candle time and price).

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": {
      "p1": "<p1>",
      "p2": "<p2>"
    },
    "name": "draw_trend_line"
  }
}

Input Schema

NameRequiredDescriptionDefault
p1Yes
p2Yes
colorNoHex colour, e.g. #ff1744 red, #00c853 green
widthNo
extend_rightNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it says nothing about persistence of the drawing, whether it requires auth, what happens on invalid time values, or what is returned. It conveys only the geometric primitive, leaving the mutation and lifecycle behavior undisclosed.

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?

A single tight sentence with the core geometric constraint front-loaded and no filler. It is concise to a fault, but nothing in it is wasted or buried.

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?

For a 5-parameter mutation tool with nested objects, no annotations, and no output schema, the description is far too thin. An agent cannot tell what the call produces, how optional styling parameters behave, or how the drawing integrates with list_drawings/get_drawing.

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 only 20% across five parameters, so the description must compensate; it clarifies that points use exact candle time and price, but says nothing about color, width (1-6), or extend_right. Three optional parameters remain undocumented in both the schema and the description.

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 verb and resource ('Draw a straight line between two points') and clarifies the coordinate basis ('exact candle time and price'), which differentiates it from draw_horizontal_line. It does not explicitly name a sibling alternative, but the two-point scope is unambiguous.

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?

There is no guidance on when to choose this over draw_horizontal_line, draw_chain, or suggest_chain, and no stated preconditions such as an active chart or symbol context. The usage is only inferable from the tool name and the two-point requirement.

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