Skip to main content
Glama
screener-mcp
by LogeshR15

screen_stocks

Read-only

Run stock screens that combine Screener.in fundamental fields with technical price-action clauses using AND/OR logic, returning matching Indian equities with optional peer comparisons.

Instructions

Run a stock screen: Screener.in fundamental fields and/or technical (price-action) clauses, combined with AND, OR and parentheses.

Fundamental fields (Screener.in syntax, exact spelling matters): Market Capitalization, Current Price, Price to Earning, Price to book value, Return on capital employed, Return on equity, Debt to equity, Sales growth 5Years, Sales growth 3Years, Sales growth last year, Profit growth 5Years, Profit growth 3Years, Profit growth last year, Dividend yield, Pledged percentage, Net cash flow last year, Average return on equity 5Years, Average return on capital employed 5Years, Current ratio, EV / EBITDA, PEG Ratio

Technical clauses (evaluated from daily price history): 52 week low distance < 10 — % above the 52-week low 52 week high distance > 30 — % below the 52-week high RSI < 30 — 14-day RSI Price above 200 DMA — also: below, 20/50/200 DMA, "50 DMA above 200 DMA" Price vs 50 DMA < -5 — % above(+)/below(−) a DMA Volume vs 20 day average > 2 — today's volume ÷ 20-day average (spike detection)

Operators: > < >= <= =, combined with AND / OR and parentheses, e.g. "(Return on capital employed > 20 OR Return on equity > 25) AND Debt to equity < 0.5" "Return on capital employed > 15 AND (RSI < 30 OR 52 week low distance < 5)" Purely fundamental OR logic runs natively on Screener; when technical clauses sit under an OR, each alternative runs as its own screen (up to 6) and results are merged — each result lists matched_groups.

Result hygiene (on by default): min_market_cap: ₹ Cr floor added to the Screener query unless the query already has a Market Capitalization clause (0 = off) exclude_flagged: drop rows with implausible numbers (P/E < 1, >500% profit spike on a small base, profit > sales, negligible sales, sub-₹1 price) — they're listed in excluded_for_data_quality. False = keep them, flagged.

peer_relative: add each result's P/E and ROCE vs its industry median (first 20 results; slower — one industry fetch per industry).

How it runs: fundamental clauses go to Screener.in (login required); technical clauses are then checked against up to max_candidates of those matches. With only technical clauses, candidates come from a public NSE index — universe (default "nifty500"; also nifty50, midcap100, smallcap100, smallcap250, bank, it, auto, pharma, fmcg, metal, realty, energy, defence, chemicals, ...) — so no login is needed.

sort_by: a technical metric (rsi14, pct_above_52w_low, volume_vs_20d_avg, ...) or a result column name. Default: the first technical filter.

page: 1-based page of results, limit per page (page=2 → results 26-50 with the default limit).

Returns partial=true (with a reason) if only some candidates could be checked — e.g. more fundamental matches than max_candidates.

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": {
      "query": "<query>"
    },
    "name": "screen_stocks"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
limitNo
orderNodesc
queryYes
sort_byNo
universeNo
peer_relativeNo
max_candidatesNo
min_market_capNo
exclude_flaggedNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description goes far beyond that by disclosing login requirements, the up-to-6 merged screens for OR'd technical clauses with matched_groups in results, the default result-hygiene filters and where dropped rows go, the performance cost of peer_relative, and the partial=true signal with its cause. These are exactly the traits that change how an agent should call and interpret the tool.

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?

Front-loaded with a one-sentence summary, then organized into labeled sections (fields, technical clauses, operators, hygiene, execution, pagination) so an agent can scan to what it needs. The long enumerations of fundamental fields and technical clause syntax are justified because exact spelling matters, though the description is near the upper bound of reasonable length.

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?

For a 10-parameter tool with branching execution paths and OR-merge logic, nothing essential is missing: query grammar, execution prerequisites, defaults that silently alter results, latency trade-offs, and the partial-result condition are all covered, and an output schema handles return shape. An agent could call it correctly on the first attempt from this text alone.

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 description coverage is 0%, so the description must carry all nine optional parameters — and it does: query syntax and exact field spellings, universe values enumerated with the nifty500 default, sort_by accepting technical metrics or column names, page/limit semantics with a worked example, min_market_cap's ₹ Cr floor and its interaction with an existing Market Capitalization clause, exclude_flagged's off-switch, peer_relative scope, and max_candidates' role. Only `order` goes undocumented, which is a minor gap against an otherwise comprehensive mapping.

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 opening line gives a specific verb and resource ('Run a stock screen') plus the exact domain: Screener.in fundamental fields combined with technical price-action clauses under AND/OR/parentheses. The scope is unmistakable. It never contrasts itself with screen_by_theme, so an agent must infer how the general screen differs from the theme-specific sibling.

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

Usage Guidelines4/5

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

Strong conditional guidance on execution paths: fundamental clauses go through Screener.in and require login, while technical-only queries draw candidates from the `universe` NSE index and need no login. The 6-alternative OR merge behavior is also spelled out. There is no explicit statement of when to prefer a sibling tool or when this screen is inappropriate, which keeps it below a 5.

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