TradingView MCP

Overview Schema Source Related Servers Discussions Admin

Inspect market data capabilities

market_get_capabilities

Read-onlyIdempotent

Check configured providers, browser authentication availability, runtime state, and currently loaded chart to choose a fitting data workflow before proceeding.

Instructions

Report configured providers, browser authentication availability, lazy-runtime state, and the currently loaded chart. Use this before choosing a data workflow.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 20, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, idempotentHint=true, destructiveHint=false. Description supplements with current chart state and browser auth checks, adding important context. No contradiction with annotations.

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 sentences, frontloading: reports first, then the specific use. All words are information-dense.

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 no-parameter inspection tool of market capabilities, coverage of internal capabilities and workflow placement is fully present; the output shape is not needed here.

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?

Tool uses zero parameters; the schema contains no properties and params are captured at 100% coverage, so the baseline for zero-parameter tools is 4.

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?

Description uses specific verbs and resources ('Report configured providers, browser authentication availability, lazy runtime state, and currently loaded chart') and gives distinct capability from market data tools. Use of 'Use this before choosing a data pipeline' reinforces intent.

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?

States when to use: 'Use this before choosing a data workflow.' It does not clearly spell out when to use alternatives, but among siblings like market_get_quotes and chart tools, this is a meta-inspection tool for providers/auth/chart state and is appropriately positioned.

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