LuxAlgo MCP

Vela chart

chart_open

Read-only

Shows an interactive live chart from Vela, our next-generation charting platform, inside the chat: crypto candles streamed from Hyperliquid or Binance in the user's browser, with optional native indicators, horizontal levels, shaded zones and a date range. Use it when the user wants to see or discuss a crypto market visually. Returns a chart_id; change or read the open chart afterwards with chart_command rather than opening a new one. This result describes the chart in words and carries no prices; once the chart is on screen, chart_command (including its read op) also returns the last price, the day's change, the visible high and low and each indicator's latest value. It never returns candles. Symbols: "BTC" or "hyperliquid:BTC" (Hyperliquid perpetuals), "binance:BTCUSDT" (Binance spot); a bare pair ending in USDT/USDC goes to Binance.

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>",
      "context": "<context>"
    },
    "name": "chart_open"
  }
}

Input Schema

Name	Required	Description	Default
`range`	No	Visible date range, ending on the newest candle.
`zones`	No	Price zones to shade.
`levels`	No	Horizontal levels to draw.
`symbol`	Yes	e.g. "BTC", "hyperliquid:ETH", "binance:BTCUSDT".
`context`	Yes	Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
`timeframe`	No	Candle timeframe.	4h
`indicators`	No	Native indicators to add.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations only say readOnlyHint/openWorld/non-destructive, but the description adds real behavioral facts: it opens a live streaming chart in the user's browser, returns a chart_id, and the result 'describes the chart in words and carries no prices' and 'never returns candles'. That pre-empts the most likely agent misread — expecting price data back.

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?

Purpose and routing come first, then return-value behavior, then symbol syntax — a sensible order with no filler. Slightly repetitive in the middle where it states twice, in different words, that the result carries no prices and that chart_command supplies them.

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 7 parameters and no output schema, the description does the important work: it explains what the call returns, what it does not, and how to follow up. Minor gaps remain, such as whether opening a chart replaces or adds to existing open charts, and no mention of the timeframe default that the schema declares.

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 100%, so baseline is 3; the description earns an extra point by documenting symbol resolution rules ('BTC' = Hyperliquid perpetuals, 'binance:BTCUSDT' = spot, bare USDT/USDC pair routed to Binance) that go beyond the schema's brief examples. It does not touch defaults for timeframe or the maximum item counts, but those are already in the schema.

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 — 'Shows an interactive live chart from Vela ... inside the chat' — and enumerates what the chart can contain (candles, indicators, levels, zones, date range). It also names the sibling it is not: chart_command is for changing or reading an already-open chart.

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

Usage Guidelines5/5

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

'Use it when the user wants to see or discuss a crypto market visually' gives an explicit trigger, and 'change or read the open chart afterwards with chart_command rather than opening a new one' gives an explicit when-not plus the alternative. Routing between chart_open and chart_command is fully determined.

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

All LuxAlgo MCP 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.