EL7.AI

Sector and industry ranking by EL7 score

el7_sector_overview

Read-only

Ranks the 11 sectors (or ~150 industries) by cap-weighted EL7 score with the seven factor axes, tier and sector-ETF returns; slug adds the top stocks and EL7's written narrative (Arabic only). US only; for Tadawul use el7_stock_rank with market=sa. Scores and returns, no prices. A single stock: el7_stock_profile.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "el7_sector_overview"
  }
}

Input Schema

Name	Required	Description	Default
`lang`	No	Output language: 'en' (default) or 'ar' for EL7's stored Arabic text.
`slug`	No	A sector slug (technology, financial-services, healthcare, ...) or industry slug (software-infrastructure, ...) for the detail view with top stocks. Omit for the ranked list.
`limit`	No	List mode: rows to return (1-50, default 20).
`scope`	No	sector = the 11 market sectors; industry = the ~150 industries.	sector
`top_stocks`	No	Detail mode: how many top-scoring stocks to list (1-20, default 10).

Output Schema

Name	Required	Description
`mode`	Yes
`as_of`	No	Source freshness: the newest source timestamp behind this result, or null when none is verified. Never request time.
`items`	Yes
`scope`	Yes
`detail`	Yes
`score_method`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral context beyond that: output is 'scores and returns, no prices', the narrative is Arabic only, and coverage is US-only – all facts an agent cannot infer from annotations.

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?

Front-loaded with the core verb and resource, followed by tightly compressed clauses and fragments that each carry distinct information (mode, regional scope, sibling routing, payload exclusions). No redundant restatement of schema fields.

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?

With an output schema present, the description need not document return values, and it covers scope, modes, and alternatives adequately. Minor gaps remain: 'tier' is not defined and sort ordering within the ranking is not stated, though neither blocks correct invocation.

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 100%, so the baseline is 3, but the description adds genuine meaning by explaining the slug-driven mode switch (detail view with top stocks and EL7's Arabic narrative) versus omitting slug for the ranked list. It also flags the Arabic-only caveat on the narrative, which interacts with the lang parameter in a way the schema does not spell out.

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?

States a specific verb and resource (ranks the 11 sectors or ~150 industries by cap-weighted EL7 score) and enumerates the payload contents: seven factor axes, tier, and sector-ETF returns. It explicitly distinguishes itself from siblings, naming el7_stock_rank and el7_stock_profile so an agent can route without opening schemas.

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

Usage Guidelines5/5

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

Gives concrete when-to-use and when-not-to-use guidance: 'US only; for Tadawul use el7_stock_rank with market=sa' and 'A single stock: el7_stock_profile.' It also explains the two modes (list vs. detail via slug) and what changes in each.

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

All EL7.AI tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?