Skip to main content
Glama
Sign In
TradingView MCP

TradingView MCP

by madiver
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

replay_trade

Execute buy, sell, or close trade actions in replay mode to practice trading decisions on TradingView charts.

Instructions

Execute a trade action in replay mode (buy, sell, or close position)

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": {
      "action": "<action>"
    },
    "name": "replay_trade"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesTrade action: buy, sell, or close

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description must carry full behavioral disclosure. It states it 'executes' a trade but does not clarify whether this is simulated or affects real positions, what side effects occur, or what the response contains. A mutation tool with zero annotation coverage should provide more context.

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?

One concise sentence with no waste. The core purpose is front-loaded, though it lacks additional detail that could be added in a structured way.

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?

Given this is a trade-execution tool with no output schema and no annotations, the description is underspecified. It should mention whether replay mode is active or auto-started, how it interacts with existing positions, and any potential side effects. The minimal description leaves agents without enough context for correct invocation.

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 description coverage is 100%—the parameter 'action' is fully documented with its possible values. The description adds no additional meaning beyond the schema, so a baseline of 3 is appropriate.

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 clearly states the tool executes a trade action in replay mode, with a specific verb and resource. It names the actions (buy, sell, close), and the 'replay mode' scope distinguishes it from siblings like replay_start/replay_stop and from real order tools.

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?

No guidance on when to use this tool versus alternatives, such as place_order/close_position for live trading, or replay_start to begin a session. It does not mention prerequisites (e.g., must have an active replay session) or exclusions.

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

Deploy Server

Other Tools