TraderWAI Charts

Get OHLC Data

get_ohlc

Read-only

Returns OHLC candles (open, high, low, close and open time in unix seconds) for a symbol and timeframe from the TraderWAI market feed, updated every minute, with the period high and low and the current price. Up to 500 candles; from/to select a time range. How far back a range can go depends on the TraderWAI account; the latest candles are available on every 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>"
    },
    "name": "get_ohlc"
  }
}

Input Schema

Name	Required	Description
`to`	No	End of time range. ISO 8601 (e.g. "2026-04-19T00:00:00Z") or unix seconds. Only candles at or before this time are included.
`from`	No	Start of time range. ISO 8601 (e.g. "2026-04-01T00:00:00Z") or unix seconds. Only candles at or after this time are included. How far back a range can go depends on the TraderWAI account; the latest candles (without from/to) are available on every account.
`limit`	No	Number of candles to return (default 100, max 500). Returns the most recent candles within the time range.
`symbol`	Yes	Trading symbol (e.g. EUR_USD, XAU_USD, BTC_USD, NAS100_USD).
`timeframe`	Yes	Candle timeframe: M1, M5, M15, M30, H1, H2, H4, H6, H8, H12, or D.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 27, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover read-only and open-world traits, and the description adds real behavioral context on top: data refreshes every minute, hard cap of 500 candles, and an account-dependent backfill limit that will silently constrain results. Return field semantics (unix-second open time, period high/low, current price) are also disclosed.

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 dense sentences, front-loaded with what is returned before the range constraints. Minor redundancy with the schema on the 500-candle cap and from/to behavior, but nothing extraneous.

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

Completeness4/5

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

With no output schema, the description usefully enumerates the returned fields and the timestamp format, plus refresh cadence and the account-gated history limit. An agent can call it correctly; only the exact response shape (e.g. array vs. object, error behavior on invalid symbols) is left unstated.

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

Parameters3/5

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

Schema coverage is 100%, so every parameter including from/to, limit, symbol, and timeframe enum values is already documented. The description only echoes the 500-candle cap and range semantics already present in the schema, adding no new syntax or edge-case guidance.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (returns OHLC candles) with the scoping dimensions (symbol, timeframe) and the data source. The candle/time-range framing cleanly separates it from siblings like get_quote (single price) and get_chart (rendered chart) without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains how to use it: 'from/to select a time range', default behavior returns the latest candles, and history depth depends on the account tier. It does not explicitly name alternatives (e.g. get_quote for a single price), so routing is inferred rather than stated.

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

All TraderWAI Charts tools Inspect

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

Need Help?