LunaTerminal

Stock screener

screen_stocks

Read-onlyIdempotent

Screen stocks on up to 20 fundamentals, each with an optional minimum and maximum (market cap in billions; growth, yield, margins and returns in percent). Returns matching stocks with price, change, market cap, P/E, forward P/E and EPS.

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

Input Schema

Name	Required	Description
`limit`	No	Rows to return, default 25.
`pbMax`	No	Maximum price to book.
`pbMin`	No	Minimum price to book.
`peMax`	No	Maximum trailing P/E.
`peMin`	No	Minimum trailing P/E.
`psMax`	No	Maximum price to sales.
`psMin`	No	Minimum price to sales.
`capMax`	No	Maximum market cap in billions of dollars.
`capMin`	No	Minimum market cap in billions of dollars.
`pegMax`	No	Maximum PEG ratio.
`pegMin`	No	Minimum PEG ratio.
`roaMax`	No	Maximum return on assets, %.
`roaMin`	No	Minimum return on assets, %.
`roeMax`	No	Maximum return on equity, %.
`roeMin`	No	Minimum return on equity, %.
`betaMax`	No	Maximum beta.
`betaMin`	No	Minimum beta.
`roicMax`	No	Maximum return on invested capital, %.
`roicMin`	No	Minimum return on invested capital, %.
`evSalesMax`	No	Maximum EV/sales.
`evSalesMin`	No	Minimum EV/sales.
`divYieldMax`	No	Maximum dividend yield, %.
`divYieldMin`	No	Minimum dividend yield, %.
`evEbitdaMax`	No	Maximum EV/EBITDA.
`evEbitdaMin`	No	Minimum EV/EBITDA.
`epsGrowthMax`	No	Maximum EPS growth, %.
`epsGrowthMin`	No	Minimum EPS growth, %.
`forwardPeMax`	No	Maximum forward P/E.
`forwardPeMin`	No	Minimum forward P/E.
`netMarginMax`	No	Maximum net margin, %.
`netMarginMin`	No	Minimum net margin, %.
`revGrowthMax`	No	Maximum revenue growth, %.
`revGrowthMin`	No	Minimum revenue growth, %.
`debtEquityMax`	No	Maximum debt to equity.
`debtEquityMin`	No	Minimum debt to equity.
`grossMarginMax`	No	Maximum gross margin, %.
`grossMarginMin`	No	Minimum gross margin, %.
`currentRatioMax`	No	Maximum current ratio.
`currentRatioMin`	No	Minimum current ratio.
`salesGrowthQMax`	No	Maximum quarterly sales growth, %.
`salesGrowthQMin`	No	Minimum quarterly sales growth, %.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=true, so the safety profile is covered. The description adds the universe semantics (fundamentals-based filtering) and the return field list, but says nothing about result ordering, whether filters combine with AND, or what happens when zero stocks match.

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?

Two sentences, tightly packed, with the filtering model front-loaded and the return contract second. No filler wording or repetition across the two sentences.

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?

For a 41-parameter tool with no output schema, the description compensates well by enumerating the returned fields (price, change, market cap, P/E, forward P/E, EPS) and the units convention. It falls short only on result ordering, row limits, and how multiple filters compose, which an agent must still infer or discover from the schema's limit parameter.

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 coverage is 100% and every one of the 41 parameters already carries a unit-bearing description, so the baseline is 3. The description's unit notes (market cap in billions; growth, yield, margins and returns in percent) largely restate what the schema says per parameter and adds only a grouping-level summary, not new meaning.

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?

Names a specific verb and resource ('Screen stocks') and immediately scopes it ('up to 20 fundamentals, each with an optional minimum and maximum'), so the agent can tell it apart from snapshot/quote siblings. The second sentence states the returned fields, completing the picture of what the tool produces.

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

Usage Guidelines3/5

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

Usage is only implied by the word 'screen' and the min/max structure; there is no explicit statement of when to prefer this over get_stock_snapshot, get_quotes or search_symbols. It does implicitly signal that this is for filtered discovery rather than single-ticker lookup, but an agent must infer the boundary.

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

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

Resources

Need Help?