DocStoX

Screen stocks technical

screen_stocks_technical

Read-onlyIdempotent

Screen active NSE equities by a technical pattern or signal on the latest session.

Universe: active, non-suspended operating companies (ETFs and fund units excluded) with a technicals row for the latest session and at least Rs 1 crore traded in the latest price session. Every row carries session_date, so the answer states which session the indicators reflect (price_date is the close used for ltp and traded value). death_cross, MACD, Bollinger and 52-week-low screens are available through screen_advanced.

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": "screen_stocks_technical"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Max rows to return (1-100).
`signal`	No	breakout_52w_high = closed at a new 52-week high in the latest session, ranked by volume vs its 20-day average. Pass exactly one of pattern or signal.
`pattern`	No	golden_cross = 50-day SMA crossed above the 200-day SMA within the last ~10 sessions and is still above, newest cross first; rsi_oversold = 14-day RSI below 30, lowest first; rsi_overbought = RSI above 70, highest first; supertrend_bullish = Supertrend uptrend, strongest trend (ADX) first. Pass exactly one of pattern or signal.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 10, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive and non-open-world, so the safety bar is low. The description adds substantive behavioral context beyond that: exact universe filters, the liquidity threshold, that every row carries session_date, and that price_date is the close used for ltp and traded value.

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 purpose, then universe, then the session_date/price_date caveat and the sibling routing. Every sentence carries information, though the parenthetical detail about technicals rows and traded value is slightly dense for a reader skimming.

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 format need not be explained, and the description covers universe, staleness (session_date), and the alternative tool. What remains implicit is whether an empty result set is normal and the default ranking when no pattern/signal is passed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the schema already documents limit, signal and pattern with ranking semantics, so the baseline is 3. The description reinforces the 'latest session' framing but adds no parameter syntax or format detail the schema lacks.

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?

Specific verb (Screen) plus resource (active NSE equities) and scope (latest session, technical pattern or signal). It explicitly names the sibling screen_advanced and enumerates which screens live there, so an agent can separate this tool from the sibling without opening either schema.

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?

It states the universe that qualifies (active, non-suspended operating companies with a technicals row and >= Rs 1 crore traded) and routes death_cross/MACD/Bollinger/52-week-low needs to screen_advanced. It does not spell out when to prefer this over screen_patterns or screen_stocks, but the context is clear.

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

All DocStoX 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.