Skip to main content
Glama
kumarakshay2456

tradingview-mcp-india

egx_stock_screener

Screens and ranks EGX stocks by score to identify strong stocks with actionable setups. Filter by timeframe, index, and minimum score.

Instructions

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

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 limit: Number of results (max 50)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
timeframeNo1D
min_scoreNo
index_filterNo
limitNo
Behavior2/5

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

No annotations are provided to indicate read-only or destructive behavior. The description does not disclose data source, latency, rate limits, or whether results are real-time. For a ranking engine, these details are important for proper usage.

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 concise, with a clear purpose statement followed by a structured list of parameters. There is no unnecessary text. However, it could be better organized with distinct sections.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema is provided, and the description does not explain the return format (e.g., list of stocks with scores, key fields). For a screening tool, this is a significant gap that reduces completeness.

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?

Despite 0% schema coverage, the description documents each parameter with allowed values and defaults (e.g., timeframe options, min_score range 0-100, index_filter list, limit max 50). This adds significant meaning beyond the bare 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 it is a 'stock ranking engine for EGX' that 'finds strong stocks with actionable setups'. This differentiates it from siblings like 'top_gainers' or 'volume_breakout_scanner', though it could be more specific about what constitutes 'actionable setups'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternative scanners or analysis tools. It does not mention prerequisites, exclusions, or scenarios where other tools would be more appropriate. Usage is only implied by the purpose statement.

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

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