Skip to main content
Glama
screener-mcp
by LogeshR15

get_52_week_low_candidates

Read-only

Find quality stocks trading near their 52-week low by filtering on ROCE, debt-to-equity, market cap, and distance above the low.

Instructions

Quality stocks trading near their 52-week low — in one call.

Combines quality filters (ROCE, debt-to-equity, market cap in ₹ Cr) with proximity to the 52-week low, and returns for each match: current price, 52W high/low, % above the low, RSI/DMA context, and the same clean fields as get_company_overview (P/E, ROCE, ROE, book value, dividend yield, debt-to-equity).

With a Screener login and no universe, scans the whole market via a Screener query. Otherwise scans an index's constituents (default Nifty 500) and computes debt-to-equity from each match's latest balance sheet.

Examples: get_52_week_low_candidates() get_52_week_low_candidates(min_roce=20, max_debt_to_equity=0.2, max_pct_above_52w_low=5) get_52_week_low_candidates(universe="midcap100", min_market_cap=5000)

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

Input Schema

NameRequiredDescriptionDefault
limitNo
min_roceNo
universeNo
min_market_capNo
max_debt_to_equityNo
max_pct_above_52w_lowNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A4/5.0
Behavior4/5

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

Annotations only give readOnlyHint and openWorldHint; the description adds genuine context — that full-market scanning requires a Screener login, that index-mode computes debt-to-equity from each match's latest balance sheet, and what fields come back. Authentication and computation-path disclosure are exactly the kinds of traits annotations cannot convey.

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 the value proposition, then filters, then mode behavior, then compact examples — a good hierarchy with no filler sentences. Slightly dense line-wrapping and three examples are on the generous side, but each still demonstrates a distinct mode or filter set.

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, return values need not be explained, yet the description still lists the key returned fields. For a six-parameter, zero-coverage schema the only omissions are `limit` and stated defaults; otherwise an agent has enough to call it correctly.

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 description coverage is 0%, so the description carries the full burden and mostly does: it names `universe` semantics and default, `min_roce`, `max_debt_to_equity`, `max_market_cap` (with ₹ Cr units), and `max_pct_above_52w_low` through prose and examples. The `limit` parameter is never mentioned, and no defaults are stated, leaving a real gap.

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 pins a specific verb and resource: find quality stocks trading near their 52-week low, plus which filters and return fields are involved. It references get_company_overview to explain the shared field set but never distinguishes itself from screen_stocks, a close sibling in the catalog, so an agent must infer the boundary.

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 clearly explains the two operating modes: with a Screener login and no `universe` it scans the whole market; otherwise it scans an index's constituents (default Nifty 500). The worked examples show realistic invocations, but there is no explicit when-not-to-use guidance relative to screen_stocks or compare_to_sector.

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