Skip to main content
Glama
lightkeeper90

ultimate-tradingview-agent

egx_stock_screener

Rank EGX stocks by a 100-point hybrid score combining trend, momentum, volume, and fundamentals. Identify strong stocks scoring 70+ with complete trade setups including entry, stop, targets, and support/resistance.

Instructions

Production stock ranking engine for EGX — finds strong stocks with actionable setups.

Uses a 100-point hybrid model combining: A. Trend & Momentum (50 pts) — EMA structure, RSI, MACD, relative performance B. Confirmation (20 pts) — Volume, ADX trend strength C. Risk-Adjusted Quality (15 pts) — ATR volatility, drawdown stability D. Fundamental Overlay (15 pts) — TradingView recommendation proxy

Stocks scoring 70+ automatically get trade setups (entry, stop, targets, S/R).

Args: timeframe: One of 5m, 15m, 1h, 4h, 1D, 1W, 1M (default 1D) min_score: Minimum stock score to include (0-100, default 55) index_filter: Filter by index — EGX30, EGX70, EGX100, SHARIAH33, EGX35LV, TAMAYUZ. Leave empty for all EGX stocks. limit: Number of results (max 50)

Returns: Ranked stocks with score breakdown. Stocks >=70 include full trade plans.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
min_scoreNo
timeframeNo1D
index_filterNo
Behavior4/5

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

With no annotations, the description carries the full burden. It details the 100-point scoring model, the 70+ threshold for trade setups, and the return structure, which is substantial. However, it does not mention potential rate limits, data freshness, or any restrictions beyond the scoring logic, so it is not a perfect 5.

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 well-structured with bullet points for the scoring model, front-loading the purpose, and every sentence adds value. It is appropriately detailed for a complex tool without being bloated.

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 covers all essential aspects: purpose, scoring method, parameter semantics, and return values (ranked stocks with score breakdown, trade plans for high-scorers). Given there is no output schema, the 'Returns' section is sufficient and complete.

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?

Schema coverage is 0%, but the description fully documents all four parameters: timeframe with valid values and default, min_score with range and default, index_filter with specific indices and empty-for-all, and limit with max and default. This completely compensates for the missing schema descriptions.

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 is a 'production stock ranking engine for EGX' that 'finds strong stocks with actionable setups.' It specifies the resource (EGX stocks) and distinguishes itself from siblings like sector scans or index analysis.

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 use for stock screening and provides scoring details, but it does not explicitly say when to use this tool versus alternatives or mention exclusion criteria. There is no comparison to the many sibling tools, so usage guidance is only implied.

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/lightkeeper90/ultimate-tradingview-agent'

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