Skip to main content
Glama
henrikxyz

tradingview-finance MCP Server

by henrikxyz

query_screener

Scan stock, crypto, or forex markets with TradingView screener. Fetch technical indicators like RSI, MACD, and moving averages, plus recommendations for specific symbols.

Instructions

Query the TradingView Stock, Crypto, or Forex Screener.

This tool allows scanning across markets or fetching technical analysis indicators (like RSI, MACD, Moving Averages) and recommendations for specific symbols.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
marketNoScreener market name, e.g. "america" (US stocks), "crypto", "forex", "hongkong", "japan".america
columnsNoSpecific list of indicator or metric fields to fetch.
sort_byNoField ID to sort the results.market_cap_basic
sort_orderNoSorting direction, either "asc" or "desc".desc
limitNoMax number of results (default: 10).
filtersNoCustom filter objects to pass to the scanner (e.g., `[{"left": "name", "operation": "equal", "right": "AAPL"}]`).
filter2NoNested boolean filter conditions to pass to the scanner.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so the description carries full burden. It mentions fetching technical indicators and recommendations, implying read-only behavior. However, it does not disclose any potential rate limits, authentication needs, or side effects.

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 concise with two sentences, front-loaded with the key action, and contains no redundant or extraneous information.

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 the tool has a full output schema and 100% parameter coverage, the description provides adequate context about market scanning and technical analysis. It could mention that results return requested columns, but overall complete.

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 coverage is 100%, so parameters are already well-documented. The description adds examples of indicators (RSI, MACD) which provide some extra context, but not significantly beyond the schema.

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?

The description clearly states the tool queries a screener for stocks/crypto/forex and can fetch technical indicators and recommendations. It distinguishes from siblings like get_technicals by mentioning scanning across markets, but does not explicitly contrast.

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 implies usage for scanning markets or fetching indicators, but lacks explicit guidance on when to use versus alternative tools (e.g., get_technicals). No when-not-to-use or context conditions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/henrikxyz/tvfinance-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server