Skip to main content
Glama
Sign In
TradingView Unified MCP

TradingView Unified MCP

by daviddme
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

emergency_stop

Stop accepting new browser operations and cancel active TradingView workflows. Submitted writes cannot be undone; reconcile them after clearing.

Instructions

Stop accepting operations and cancel active browser workflows. Already submitted TradingView writes cannot be undone; reconcile them after clearing.

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": "emergency_stop"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing a real behavioral caveat: writes already submitted to TradingView survive the stop and must be reconciled manually. It does not clarify whether subsequent tool calls are rejected, what happens to queued jobs/streams, or how the stop is released, so it stops short of full disclosure.

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?

Two short sentences: the action first, the irreversibility caveat second. No filler and the most consequential fact (unrecoverable writes) is not buried.

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

Completeness3/5

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

For a safety-critical halt tool with no output schema and thin annotations, the definition covers the action and one caveat but omits what state the system enters, how an agent verifies the stop took effect (emergency_status), and how normal operation is restored.

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?

Zero parameters, so the baseline is 4. The description correctly implies the tool is parameterless and global in scope ('stop accepting operations'), with no misleading parameter hints.

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?

States a specific verb pair and effects: 'Stop accepting operations' and 'cancel active browser workflows.' An agent knows exactly what the tool does and that it is a halt operation, though it never names its siblings (emergency_status, emergency_clear) to sharpen the boundary.

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 only implied by the 'emergency' framing and the trailing clause 'reconcile them after clearing,' which hints that emergency_clear is the follow-up. There is no explicit when-to-use, when-not-to-use, or comparison against emergency_status/emergency_clear.

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