Skip to main content
Glama
trading-crew-mcp

trading-crew-mcp

draw_horizontal_line

Draws a horizontal line at a specified price on the open TradingView chart, with optional color and width for annotating support, resistance, or price levels.

Instructions

Draw a horizontal line at a 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": {
      "price": "<price>"
    },
    "name": "draw_horizontal_line"
  }
}

Input Schema

NameRequiredDescriptionDefault
colorNoHex colour, e.g. #ff1744 red, #00c853 green
priceYes
widthNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/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 burden and does almost nothing with it. It does not say whether the drawing persists across sessions, which chart it attaches to, whether it is reversible, or what a successful call returns.

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

Conciseness3/5

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

The single sentence is front-loaded and free of filler, but for a three-parameter drawing tool it is under-specified rather than genuinely concise. Brevity here costs information the agent needs.

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?

With no annotations, no output schema, and two of three parameters undocumented, the definition leaves the agent guessing about chart context, persistence, and parameter meaning. It is materially incomplete for even a simple drawing mutation.

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 33%: color has a hex hint, but price and width have no descriptions. The phrase 'at a price' only loosely identifies the price parameter as a price level, and width (1-6 range) is never explained in the description, so the coverage gap is not compensated.

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 gives a specific verb (draw) and a specific resource (a horizontal line at a price), which is enough to separate it from draw_trend_line or draw_chain. It stops short of explicitly naming a sibling or stating scope, so it is clear but not fully differentiated.

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 use this versus draw_trend_line, draw_chain, or create_alert, and no mention of prerequisites such as an active chart, symbol, or timeframe. The agent must infer all usage conditions from the tool name alone.

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