Skip to main content
Glama
shivamg194-lab

screener-mcp-server

Run a Custom Stock Screen on Screener.in

screener_run_custom_screen
Read-onlyIdempotent

Filter all listed Indian companies by fundamental criteria using Screener.in query syntax. Return matching companies based on financial ratios and growth metrics.

Instructions

Run a custom stock screen using Screener.in's query-builder syntax against 10+ years of financial data for all listed Indian companies, and return the matching companies.

This is the core "screener" feature — filter the whole market by fundamental criteria in one call, instead of checking companies one by one.

Args:

  • query (string): Screener query syntax. Combine conditions with AND/OR. Examples: "Market Capitalization > 500 AND Return on capital employed > 22" "Price to Earning < 15 AND Debt to equity < 0.5 AND Sales growth 3Years > 10" Common fields: Market Capitalization, Current Price, Price to Earning, Return on equity, Return on capital employed, Debt to equity, Sales growth, Profit growth, Dividend yield, Book value, Promoter holding.

  • limit (number, 1-100, default 25): Max rows to return. Note: without a logged-in session (SCREENER_SESSION_COOKIE env var), Screener itself caps guest results to a small number regardless of this limit.

Returns: JSON: { "columns": string[], "rows": [{name, values}], "totalFound": number|null, "truncated": boolean }

Examples:

  • Use when: "Find small-cap companies with ROE > 20% and low debt" -> query="Market Capitalization < 5000 AND Return on equity > 20 AND Debt to equity < 0.3"

  • Don't use when: You want data for one specific known company (use screener_get_company_overview instead)

Error Handling:

  • Returns "Error: Screener rejected this query: ..." if the query syntax is invalid — check field names and operators.

  • If truncated=true and totalFound is much larger than what's returned, note that a logged-in session would unlock more rows.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of result rows to return (default 25, max 100). Guest access is capped by Screener regardless of this value.
queryYesScreener.in query-builder syntax, e.g. "Market Capitalization > 500 AND Return on equity > 22". Combine conditions with AND/OR. Common fields: Market Capitalization, Current Price, Price to Earning, Return on equity, Return on capital employed, Debt to equity, Sales growth, Profit growth, Dividend yield, Book value.
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds valuable behavioral context beyond annotations: it explains the guest session cap on results, details error response formats, and describes the return structure. No contradictions with 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?

The description is well-structured with clear sections: purpose, arguments, returns, examples, and error handling. It is front-loaded with the core action. Every sentence adds value without redundancy. The length is appropriate for the complexity.

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?

Given 2 parameters with 100% schema coverage, moderate complexity (custom query syntax), and no output schema, the description is complete. It explains the query language, provides examples, covers guest limitations, details return format, and addresses error scenarios. It also references sibling tools for comparison.

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 100%, so baseline is 3. The description adds significant value by providing examples of query syntax, listing common financial fields, explaining the limit parameter's behavior under guest access, and giving practical usage patterns. This goes beyond the schema's minimal descriptions.

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?

The description clearly states it runs a custom stock screen using Screener.in's query-builder syntax against financial data and returns matching companies. It distinguishes from siblings by explicitly noting it is for screening multiple companies at once, and provides a 'Don't use when' example that names the sibling tool for individual companies.

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?

The description gives explicit when-to-use context (core screener feature) and when-not-to-use (use screener_get_company_overview for single companies). It includes example use cases and queries, error handling guidance, and notes about guest session limits. It clearly states when to prefer alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/shivamg194-lab/screener-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server