Skip to main content
Glama
Sign In

TraderWAI Charts

by com.traderwai
OverviewDiscussionsAdmin

Draw marks on a chart

draw_chart
Read-only

Renders technical-analysis marks on a TraderWAI candlestick chart and returns the image. Marks: horizontal levels, zones (supply/demand, ranges, gaps), trendlines and channels, candle markers, text labels (HH, HL, BOS, CHoCH…), Fibonacci retracements, measurements, an expected path and a trade plan (entry, stop loss and targets with R). Candles are identified by their open time in UTC (ISO 8601); a price can be a number or the high/low of a candle. Up to 30 marks per chart; marks that are not valid are skipped and listed in the result. "until" freezes the chart at a given candle. Example: {"symbol":"XAU_USD","timeframe":"H1","marks":[{"type":"zone","high":4160,"low":4152,"from":"2026-10-15T09:00:00Z","extend":true,"label":"Supply","tone":"bearish"},{"type":"hline","price":"low","from":"2026-10-15T05:00:00Z","label":"Support","tone":"bullish"},{"type":"position","side":"short","entry":4148,"stop_loss":4162,"take_profit":[4130,4110]}]}. The number of marked charts per day depends on the TraderWAI account.

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>",
      "marks": "<marks>"
    },
    "name": "draw_chart"
  }
}

Input Schema

NameRequiredDescriptionDefault
marksYesWhat to draw
untilNoOptional: draw the chart only up to this candle time (UTC ISO), e.g. the last candle you analysed
symbolYesSymbol (e.g. XAU_USD, NAS100_USD, EUR_USD).
timeframeYesChart timeframe

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the read-only/non-destructive profile, and the description adds meaningful context: it returns an image, caps marks at 30, skips and reports invalid marks, 'until' freezes the chart at a candle, and a per-day quota applies. These are behavior details beyond the annotations, though the quota is left vague ('depends on the account').

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?

The core behavior and limits are front-loaded, and the mark enumeration is dense but purposeful. The long inline JSON example is justified for a complex nested schema, though it makes the entry longer than strictly needed.

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

Completeness5/5

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

For a complex, nested, image-returning tool with no output schema, the description is complete: it explains the return type, the 30-mark cap, invalid-mark handling, the 'until' freeze, and rate limits. An agent has what it needs to call it correctly.

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 coverage is already 100%, so the baseline is 3. The description goes further with a concrete end-to-end example showing zone/hline/position marks and explains that price may be a literal or a candle anchor ('high'/'low') and that candles are UTC ISO 8601 open times, adding interpretive value over the schema.

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 specific verb and resource (renders technical-analysis marks on a candlestick chart and returns the image) and enumerates the mark families. It is very clear about what it does, but it never explicitly contrasts with siblings like get_chart or get_ohlc, which an agent needs to disambiguate plain-chart reads from annotated renders.

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 implied rather than stated: an agent infers you use this when you want annotations drawn, and the description adds operational constraints (30-mark cap, invalid marks are skipped and listed, per-account daily limit). It never explicitly says when to prefer get_chart over this or when-not to use it, leaving the main alternative routing to inference.

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

All TraderWAI Charts toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources