Skip to main content
Glama
jihjihk

QuantContext

by jihjihk

screen_stocks

Read-onlyIdempotent

Screen stocks with quantitative filters: filter by fundamentals, momentum, value, or technical signals to get ranked candidates with scores and metrics.

Instructions

Screen a stock universe with quantitative filters. Returns ranked candidates with scores and metrics.

Use this tool when you need to find stocks matching specific criteria — value stocks, momentum leaders, quality companies, or multi-factor ranked candidates. Supports 7 screen types across 3 universes (S&P 500, Russell 2000, Nasdaq 100).

After screening, use backtest_strategy to test the screen as a trading strategy, or factor_analysis to understand the factor exposures of the selected stocks.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoDate for the screen in YYYY-MM-DD format. Defaults to most recent trading day.
configNoScreen-specific configuration. Examples: fundamental_screen: {pe_lt: 15, roe_gt: 12}. momentum_screen: {lookback_days: 200, top_pct: 0.2}. value_screen: {pe_lt: 20, top_n: 30}. factor_model: {weights: {value: 0.3, momentum: 0.3, quality: 0.2, volatility: 0.2}, top_n: 20}. mean_reversion: {lookback_days: 60, z_threshold: -1.5}. All parameters are optional — sensible defaults are used.
universeNoStock universe to screen. Options: sp500, russell2000, nasdaq100sp500
screen_typeNoType of screen to run. Options: fundamental_screen (filter by PE/ROE/debt), quality_screen (filter by ROE/margins), momentum_screen (rank by price momentum), value_screen (rank by valuation), factor_model (multi-factor ranking), technical_signal (RSI/SMA/Bollinger), mean_reversion (z-score below threshold)fundamental_screen

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already show read-only and idempotent behavior. Description adds context about supporting 7 screen types across 3 universes and that parameters have sensible defaults, which helps the agent understand non-obvious traits.

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?

Concise yet informative: first sentence states purpose, then usage guidance, then examples, then post-use hints. No unnecessary words.

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?

Despite having 4 parameters and a complex config object, the description covers all aspects: parameter defaults, examples, universe options, screen types, and next-step tools. Output schema exists (not shown but referenced), so completeness is high.

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 100% with descriptions for all parameters. The description enhances this by providing example configs for each screen type, adding meaning beyond schema.

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?

Clearly states it screens stocks with quantitative filters and returns ranked candidates. Distinguishes from siblings (backtest_strategy, factor_analysis) by mentioning them as post-use tools.

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?

Explicitly tells when to use this tool ('find stocks matching specific criteria') and what to do after screening. Provides context on screen types and universes.

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/jihjihk/quantcontext-mcp-server'

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