Skip to main content
Glama
atilaahmettaner

tradingview-mcp

stock_screener

Screen stocks by common or preferred share type across global markets. Get market-cap ranked results with price, dividend yield, and more.

Instructions

Screen stocks by share type — the API twin of TradingView's "Common stock" / "Preferred stock" symbol-search filter.

Args: country: TradingView market name — e.g. america, korea, germany, brazil, japan, uk, india, turkey, canada, australia, france, hongkong stock_type: common | preferred limit: rows to return (max 2000, single upstream request), ranked by market cap descending exclude_otc: default True — drop OTC listings (foreign companies traded over-the-counter); "america" otherwise means "US venue", not "US company" compact: default False — True returns only ticker/symbol/price/currency/ change_percent per row (light payload for bulk price feeds)

Returns: Envelope dict: total_matches (market-wide count), returned, and rows of {ticker, symbol, description, exchange, price, currency, change_percent, dividend_yield, market_cap}. Prices are in the market's local currency (e.g. KRW for korea).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
compactNo
countryNoamerica
stock_typeNocommon
exclude_otcNo
Behavior5/5

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

With no annotations, the description fully discloses important behaviors: single upstream request, max 2000 rows, ranking by market cap, OTC handling, compact mode, return envelope details, and local currency pricing.

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?

The description is well-structured with Args and Returns sections and front-loaded with purpose, though it could be slightly more concise.

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?

The description is highly complete, covering return format, country list, parameter defaults, edge cases (OTC, currency), and ranking order, despite no output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite 0% schema coverage, the description adds rich meaning to all 5 parameters, including country market names, stock_type options, limit constraints, exclude_otc logic, and compact output details.

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 it screens stocks by share type and references TradingView's filter, but does not explicitly differentiate from sibling tools like egx_stock_screener.

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 stock screening but provides no explicit guidance on when to use this tool versus the many sibling tools, nor any exclusions.

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/atilaahmettaner/tradingview-mcp'

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