Skip to main content
Glama

Read the marks on the live chart

get_chart_marks
Read-only

Reads the marks YOU left on the user's live chart in TraderWAI (every draw_chart call saves its marks there, per symbol, over the real-time price). Use it to continue an earlier analysis: read the marks of a symbol, adjust them and call draw_chart again with the full updated set (each draw_chart replaces the previous marks of that symbol). Without a symbol it lists the symbols that have marks. Read-only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_chart_marks"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolNoSymbol (e.g. XAU_USD). Omit to list the symbols that have marks.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish read-only/non-destructive behavior, and the description adds useful context: marks persist per symbol, draw_chart replaces the prior marks for that symbol, and omitting symbol returns the list of marked symbols. It stops short of describing the returned mark structure or error behavior, so it is strong but not exhaustive.

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

Conciseness5/5

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

The definition is front-loaded with the core action, then adds the workflow, listing behavior, and safety note without redundant padding. Every sentence contributes to invocation or interpretation.

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 low-complexity, one-optional-parameter read tool with no output schema, the description covers the resource, persistence model, listing fallback, and relationship to draw_chart. That is enough for an agent to call it correctly without needing additional context.

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?

There is one optional parameter and the schema already documents at 100% coverage that omitting symbol lists marked symbols. The description reinforces that behavior and the per-symbol scoping but adds no syntax or format details beyond 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?

The description states a specific verb ('Reads') and resource ('marks YOU left on the user's live chart'), and explicitly ties those marks to draw_chart's saved output per symbol. That makes it distinguishable from the sibling draw_chart and from generic chart-reading tools.

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?

It gives a clear when-to-use scenario: continuing an earlier analysis by reading a symbol's marks, adjusting them, and calling draw_chart with the full updated set. It also explains the no-symbol listing case, but does not explicitly state when to avoid this tool in favor of get_chart or another reader.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources