Skip to main content
Glama
Sign In
Financial Modeling Prep MCP Server

Financial Modeling Prep MCP Server

by imbenrabi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

stockScreener

Read-onlyIdempotent

Screen stocks by market cap, price, volume, beta, sector, country, and other criteria to find investments that match your strategy.

Instructions

Discover stocks that align with your investment strategy using the FMP Stock Screener API. Filter stocks based on market cap, price, volume, beta, sector, country, and more to identify the best opportunities.

Input Schema

NameRequiredDescriptionDefault
pageNoPage number for pagination
isEtfNoFilter ETFs
limitNoLimit number of results
isFundNoFilter funds
sectorNoFilter by sector (e.g., Technology)
countryNoFilter by country (e.g., US)
exchangeNoFilter by exchange (e.g., NASDAQ)
industryNoFilter by industry (e.g., Consumer Electronics)
betaMoreThanNoFilter companies with beta greater than this value
betaLowerThanNoFilter companies with beta less than this value
priceMoreThanNoFilter companies with price greater than this value
priceLowerThanNoFilter companies with price less than this value
volumeMoreThanNoFilter companies with volume greater than this value
volumeLowerThanNoFilter companies with volume less than this value
dividendMoreThanNoFilter companies with dividend greater than this value
avgVolumeMoreThanNoFilter companies with average volume greater than this value
dividendLowerThanNoFilter companies with dividend less than this value
isActivelyTradingNoFilter actively trading companies
marketCapMoreThanNoFilter companies with market cap greater than this value
avgVolumeLowerThanNoFilter companies with average volume less than this value
marketCapLowerThanNoFilter companies with market cap less than this value
includeAllShareClassesNoInclude all share classes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.9.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed3 schema fields changedv2.8.0
    • addedInput schema / properties / avgVolumeLowerThan
      Added value: +{
+  "description": "Filter companies with average volume less than this value",
+  "type": "number"
+}
    • addedInput schema / properties / avgVolumeMoreThan
      Added value: +{
+  "description": "Filter companies with average volume greater than this value",
+  "type": "number"
+}
    • addedInput schema / properties / page
      Added value: +{
+  "description": "Page number for pagination",
+  "type": "number"
+}
  3. First observed

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is known. The description adds no behavioral context beyond that—it does not describe pagination behavior, defaults, result ordering, rate limits, or how multiple filters combine.

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?

The description is short and front-loaded, with the core action and filter scope stated immediately. Some marketing phrasing ('align with your investment strategy', 'identify the best opportunities') is less useful than concrete usage detail, but the description remains efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a relatively complex tool with 22 optional filter parameters and no output schema, yet the description does not explain what the response contains, whether all parameters are optional, default pagination or limit behavior, or how results are sorted. It is therefore too thin for the tool's complexity and leaves the agent to infer important invocation details from the schema alone.

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 description coverage is 100%, so every parameter already has documented meaning in the schema. The description mentions several filter dimensions (market cap, price, volume, beta, sector, country) but adds no units, ranges, defaults, combination semantics, or other meaning beyond what the schema provides.

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 description states a specific verb and resource: discover stocks via a stock screener and filter by criteria such as market cap, price, volume, beta, sector, and country. It is clearly a screening tool and is distinguishable from sibling list/get/search tools by name and purpose, though it does not explicitly contrast itself with any sibling.

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 implied by the phrase 'align with your investment strategy' and the list of filter categories, so an agent can infer this is the tool for building filtered stock universes. However, it gives no explicit when-to-use guidance versus alternatives like searchSymbol, getActivelyTradingList, or getMostActiveStocks, and no when-not-to-use conditions.

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

Deploy Server

Other Tools