Skip to main content
Glama

screen_stocks

Screen stocks and ETFs by fundamental criteria like sector, market cap, beta, and dividend to narrow results.

Instructions

Screen stocks by fundamental criteria (sector, market cap, beta, dividend, etc.).

Searches the full universe of stocks and ETFs using financial filters. Combine multiple criteria to narrow results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of results (default: 50).
formatNoOutput format. Exposed as Literal["full", "summary"]; values are case-sensitive: - "summary": Key metrics per result (symbol, name, sector, market cap, price, beta) - "full": All available fields from the screenersummary
is_etfNoSet to true to screen ETFs only, false for stocks only.
sectorNoSector filter (e.g., "Technology", "Healthcare", "Energy").
countryNoCountry filter (e.g., "US", "GB", "JP").
is_fundNoSet to true to screen funds only, false to exclude funds.
beta_maxNoMaximum beta.
beta_minNoMinimum beta (market sensitivity).
exchangeNoExchange filter (e.g., "NASDAQ", "NYSE", "LSE").
industryNoIndustry filter (e.g., "Software", "Biotechnology").
price_maxNoMaximum stock price.
price_minNoMinimum stock price.
volume_maxNoMaximum average daily volume.
volume_minNoMinimum average daily volume.
dividend_maxNoMaximum annual dividend per share.
dividend_minNoMinimum annual dividend per share.
market_cap_maxNoMaximum market capitalization in USD.
market_cap_minNoMinimum market capitalization in USD (e.g., 10000000000 for $10B).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

No annotations provided, so description carries full burden. Describes search and filtering behavior but does not explicitly state read-only nature, limitations, authentication, or rate limits. Adequate but lacks depth.

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, front-loaded with purpose, no fluff. Efficiently communicates the tool's function and usage.

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?

Given 18 parameters (none required) and existence of output schema, description adequately explains the tool's capability. Could be slightly more explicit about return format, but output schema covers that.

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%. Description only lists a few criteria ('sector, market cap, beta, dividend') without adding meaning beyond the detailed schema descriptions. Baseline score of 3.

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?

Clearly states 'Screen stocks by fundamental criteria' with examples, distinguishing from siblings like 'compare_peers' or 'screen_estimate_revisions'. Could be more specific about what 'screen' entails (filter and return results).

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?

Provides context: 'Searches the full universe of stocks and ETFs' and 'Combine multiple criteria to narrow results.' No explicit when-not or alternatives, but is adequate for a filtering tool.

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/henrysouchien/fmp-mcp'

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