Skip to main content
Glama
screener-mcp
by LogeshR15

screen_by_theme

Read-only

Run pre-built thematic stock screens across Indian equities, filtering by value, growth, quality, dividend or sector themes such as defense, chemicals and renewable energy.

Instructions

Run a pre-built thematic stock screen.

Query themes run a Screener query across the whole market. Sector themes
(defense, ev_theme, chemicals, railways, renewable_energy) start from the
companies actually in the sector — NSE index constituents, Screener
industry pages or a curated list — then apply the filters; the response's
data.universe says exactly which.

Themes and criteria:
  undervalued_small_cap — Small caps (< ₹5000 Cr) with ROCE > 15%, low debt, P/E < 20
      Market Capitalization < 5000 AND Return on capital employed > 15 AND Debt to equity < 0.5 AND Profit growth 3Years > 10 AND Price to Earning < 20
  high_roce_low_debt — ROCE > 20%, debt-to-equity < 0.3, 5-year profit growth > 12%
      Return on capital employed > 20 AND Debt to equity < 0.3 AND Profit growth 5Years > 12
  compounders — 15%+ five-year sales and profit growth with ROE and ROCE > 15%, low debt
      Sales growth 5Years > 15 AND Profit growth 5Years > 15 AND Return on equity > 15 AND Debt to equity < 0.5 AND Return on capital employed > 15
  turnaround — Strong recent profit recovery on growing sales
      Profit growth 3Years > 25 AND Profit growth last year > 20 AND Sales growth 3Years > 10 AND Return on capital employed > 10
  rising_profit_falling_price — Profits up 15%+ a year over 3 years while the share price fell over the last year, P/E < 15
      Profit growth 3Years > 15 AND Sales growth 3Years > 10 AND Return over 1year < 0 AND Price to Earning < 15
  improving_roce — ROCE > 15% and higher than both last year's and its 5-year average
      Return on capital employed > 15 AND Return on capital employed > Return on capital employed preceding year AND Return on capital employed > Average return on capital employed 5Years AND Debt to equity < 1
  hidden_gems — Small cap (< ₹5000 Cr), ROCE > 15%, 5-year sales growth > 15%, low debt
      Market Capitalization < 5000 AND Return on capital employed > 15 AND Sales growth 5Years > 15 AND Debt to equity < 0.5
  dividend_aristocrats — Yield > 2%, a dividend paid in each of the last two years and a 3-year average payout > 20%, with ROE > 12% and low debt (Screener has no longer dividend-streak field)
      Dividend yield > 2 AND Dividend last year > 0 AND Dividend preceding year > 0 AND Average dividend payout 3years > 20 AND Return on equity > 12 AND Debt to equity < 0.5
  qarp — Quality at a reasonable price: P/E < 25, ROE > 15%, profit growth > 12%, low debt, > ₹1000 Cr
      Price to Earning < 25 AND Return on equity > 15 AND Profit growth 5Years > 12 AND Debt to equity < 0.5 AND Market Capitalization > 1000
  micro_cap_growth — Micro caps (< ₹1000 Cr) with 20%+ three-year sales and profit growth, ROCE > 15%
      Market Capitalization < 1000 AND Sales growth 3Years > 20 AND Profit growth 3Years > 20 AND Return on capital employed > 15
  defense — Defence companies (Nifty India Defence + Screener's Aerospace & Defense and Shipbuilding industries) with ROCE > 12%
      sector universe; filters: Market Capitalization > 500 AND Return on capital employed > 12
  ev_theme — Nifty EV & New Age Automotive constituents (EV makers, batteries, auto components) with ROCE > 12%
      sector universe; filters: Market Capitalization > 1000 AND Return on capital employed > 12
  chemicals — Specialty chemicals (Screener's Specialty Chemicals industry + Nifty Chemicals) with ROCE > 15%
      sector universe; filters: Market Capitalization > 500 AND Return on capital employed > 15
  railways — Railway companies (Screener's Railway Wagons industry + a curated list of railway PSUs and suppliers) with ROCE > 12%
      sector universe; filters: Market Capitalization > 500 AND Return on capital employed > 12
  renewable_energy — Renewable energy (curated list: wind/solar equipment makers and green power producers) with ROCE > 10%
      sector universe; filters: Market Capitalization > 500 AND Return on capital employed > 10

limit: results per page (default 20)
page: 1-based page of results

Examples:
  screen_by_theme("hidden_gems")
  screen_by_theme("defense")
  screen_by_theme("compounders", page=2)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "theme": "<theme>"
    },
    "name": "screen_by_theme"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
limitNo
themeYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuinely useful behavior beyond that: it explains that sector themes start from an index/industry/curated universe and that the response's data.universe reports which one was used, plus pagination defaults. Minor gap: no note on result ordering or typical result volume.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Structure is good — purpose first, then the theme catalog, then params, then examples — and the enumeration is justified by the missing enum in the schema. However, each theme is stated twice (a prose gloss plus the raw filter expression), which is substantial redundancy across sixteen entries and bloats the definition considerably.

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?

An output schema exists, so return values needn't be explained, and the description still adds the useful data.universe pointer. Given three simple parameters and one required string, the definition gives an agent everything needed to pick a valid theme and page through results. Only missing piece is any indication of expected result counts or how to handle an unrecognized theme string.

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% and there are no enums, so the description carries the full load — and it does: every valid theme string is enumerated with its exact criteria, which is the single most important thing an agent needs. 'limit' and 'page' semantics are briefly stated (default 20, 1-based). It stops short of stating valid range or maximum for limit.

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?

Opens with a specific verb and resource: 'Run a pre-built thematic stock screen', and immediately explains that themes come in two flavors (market-wide query themes vs. sector-universe themes). This clearly separates it from a general screener like screen_stocks, though the sibling is never named explicitly.

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 when to use it (you want a canned theme rather than custom filters) via the 'pre-built' framing and the query-vs-sector universe distinction, but it never states when NOT to use it or names screen_stocks as the alternative for custom criteria. The examples show invocation but not selection logic.

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