Skip to main content
Glama
Sign In
TradingView OpenCode Agent

TradingView OpenCode Agent

by jadatorin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

quote_get

Retrieve current price and OHLC data for any TradingView symbol to analyze market conditions.

Instructions

Get current quote (price, OHLC) for a symbol

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

Input Schema

NameRequiredDescriptionDefault
symbolYesTradingView symbol (e.g., BINANCE:BTCUSDT)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description must convey behavioral traits. It discloses that the tool returns current quote (price, OHLC), which is moderately informative. However, it does not specify if the quote is real-time or delayed, any authentication requirements, or side effects. The description adds some context but lacks depth.

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 description is a single, well-structured sentence that front-loads the action ('Get current quote'). Every word serves a purpose; there is no redundancy or unnecessary information. Highly concise.

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?

Given no output schema, the description adequately explains the return value (price, OHLC). The tool is simple with one required parameter. While it could mention format or potential errors, the description is sufficiently complete for common use cases.

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%, with the parameter 'symbol' already explained in the schema as a TradingView symbol. The tool description adds no additional meaning beyond the schema. Baseline score 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 gets a current quote (price, OHLC) for a symbol. The verb 'Get' and resource 'quote' are specific. Among sibling tools like data_get_ohlcv (historical) or data_get_study_values (studies), this tool's purpose is distinct and unambiguous.

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?

The description does not explicitly state when to use this tool versus its siblings. While the purpose implies it's for current price/OHLC, there is no direct guidance on alternatives (e.g., 'Use data_get_ohlcv for historical data'). Usage is implied but not clarified.

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