Skip to main content
Glama
imbenrabi

Financial Modeling Prep MCP Server

by imbenrabi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

stockScreener

Read-onlyIdempotent

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.

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

TableJSON 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. 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"
+}
  2. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds nothing beyond that: no pagination behavior, no default limit, no note on how many optional filters can be combined, no indication of result ordering or cost.

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?

Two sentences, outcome and capability front-loaded, no filler or repetition. Slightly generic marketing phrasing ('best opportunities') costs it the top mark.

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

Completeness3/5

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

Coverage is adequate for a read-only screener whose 22 filters are fully documented in the schema and whose safety traits are declared in annotations. However, with no output schema and no mention of pagination/limit defaults or result shape, an agent has to infer how to page through and what comes back.

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% across all 22 parameters, each with an inline description, so the schema does the heavy lifting and baseline 3 applies. The description's partial filter list (market cap, price, volume, beta, sector, country, 'and more') only echoes what the schema already documents.

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?

States a specific verb and resource: discover/screen stocks using the FMP Stock Screener API, and enumerates filter dimensions (market cap, price, volume, beta, sector, country). This clearly separates it from quote, constituent, or news siblings, though it never names an alternative tool directly.

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

Usage Guidelines2/5

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

The description gives only a marketing framing ('align with your investment strategy', 'identify the best opportunities') with no when-to-use, when-not-to-use, or alternative guidance. An agent choosing between this and getBiggestGainers, getMostActiveStocks, or getCompanyProfile gets no routing help.

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