Skip to main content
Glama
kumarakshay2456

tradingview-mcp-india

egx_index_analysis

Analyze EGX indexes with full technical indicators and constituent performance. Customize by timeframe and detail limit for targeted insights.

Instructions

Analyse an EGX index showing constituent performance with full indicators.

Args: index: EGX30, EGX70, EGX100, SHARIAH33, EGX35LV, TAMAYUZ timeframe: One of 5m, 15m, 1h, 4h, 1D, 1W, 1M (default 1D) limit: Number of stocks to show in detail (max 100)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
indexNoEGX30
timeframeNo1D
limitNo
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only mentions 'full indicators' without clarifying side effects, output format, or if it's read-only. The vague term 'full indicators' lacks specificity about what operations are performed.

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 one-sentence purpose followed by a parameter list. It is front-loaded and efficient, but the list format could be more clearly structured with separators or explanations.

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?

Given no annotations, no output schema, and 0% schema coverage, the description is insufficient. It lacks details on output behavior, constraints, and the nature of 'full indicators'. For a tool with three parameters, more context is needed.

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?

Schema coverage is 0%, so the description must compensate. It specifies allowed values for index and timeframe, and defines limit as 'Number of stocks to show in detail'. This adds significant meaning beyond the schema, though it could detail what 'full indicators' entails.

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 it analyzes an EGX index constituent performance with full indicators, and lists specific index values. It distinguishes from siblings like egx_market_overview (broader market) and egx_stock_screener (individual stocks).

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 provides valid index choices and parameters but does not explicitly state when to use this tool over alternatives like egx_market_overview or egx_sector_scan. It implies usage for constituent-level index analysis but lacks explicit guidance.

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