Skip to main content
Glama

Fmp

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Stock Screener

stock_screener
Read-onlyIdempotent

Stock screener (paid).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
isEtfNo"true" | "false"
limitNoMax rows (default 100). At least one filter should be set, or this is a slice of the whole exchange rather than a screen.
sectorNoe.g. "Technology", "Healthcare", "Energy", "Financial Services".
countryNo2-letter country code, e.g. "US".
exchangeNoe.g. "NASDAQ", "NYSE".
industryNoe.g. "Semiconductors", "Biotechnology".
betaMoreThanNoMinimum beta.
betaLowerThanNoMaximum beta.
priceMoreThanNoMinimum share price.
priceLowerThanNoMaximum share price.
volumeMoreThanNoMinimum average volume.
volumeLowerThanNoMaximum average volume.
dividendMoreThanNoMinimum dividend yield.
dividendLowerThanNoMaximum dividend yield.
isActivelyTradingNo"true" | "false"
marketCapMoreThanNoMinimum market cap in USD, e.g. 1000000000 for $1B+.
marketCapLowerThanNoMaximum market cap in USD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed18 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -true
    • addedInput schema / properties / betaLowerThan
      Added value: +{
+  "description": "Maximum beta.",
+  "type": "number"
+}
    • addedInput schema / properties / betaMoreThan
      Added value: +{
+  "description": "Minimum beta.",
+  "type": "number"
+}
    • addedInput schema / properties / country
      Added value: +{
+  "description": "2-letter country code, e.g. \"US\".",
+  "type": "string"
+}
    • addedInput schema / properties / dividendLowerThan
      Added value: +{
+  "description": "Maximum dividend yield.",
+  "type": "number"
+}
    • addedInput schema / properties / dividendMoreThan
      Added value: +{
+  "description": "Minimum dividend yield.",
+  "type": "number"
+}
    • addedInput schema / properties / exchange
      Added value: +{
+  "description": "e.g. \"NASDAQ\", \"NYSE\".",
+  "type": "string"
+}
    • addedInput schema / properties / industry
      Added value: +{
+  "description": "e.g. \"Semiconductors\", \"Biotechnology\".",
+  "type": "string"
+}
    • addedInput schema / properties / isActivelyTrading
      Added value: +{
+  "description": "\"true\" | \"false\"",
+  "type": "string"
+}
    • addedInput schema / properties / isEtf
      Added value: +{
+  "description": "\"true\" | \"false\"",
+  "type": "string"
+}
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Max rows (default 100). At least one filter should be set, or this is a slice of the whole exchange rather than a screen.",
+  "type": "number"
+}
    • addedInput schema / properties / marketCapLowerThan
      Added value: +{
+  "description": "Maximum market cap in USD.",
+  "type": "number"
+}
    • addedInput schema / properties / marketCapMoreThan
      Added value: +{
+  "description": "Minimum market cap in USD, e.g. 1000000000 for $1B+.",
+  "type": "number"
+}
    • addedInput schema / properties / priceLowerThan
      Added value: +{
+  "description": "Maximum share price.",
+  "type": "number"
+}
    • addedInput schema / properties / priceMoreThan
      Added value: +{
+  "description": "Minimum share price.",
+  "type": "number"
+}
    • addedInput schema / properties / sector
      Added value: +{
+  "description": "e.g. \"Technology\", \"Healthcare\", \"Energy\", \"Financial Services\".",
+  "type": "string"
+}
    • addedInput schema / properties / volumeLowerThan
      Added value: +{
+  "description": "Maximum average volume.",
+  "type": "number"
+}
    • addedInput schema / properties / volumeMoreThan
      Added value: +{
+  "description": "Minimum average volume.",
+  "type": "number"
+}
  2. First observed

TDQS

C2.3/5.0
Behavior3/5

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

The annotations already declare the tool as read-only, idempotent, and non-destructive. The description adds only the word 'paid', which is a cost/access note, but lacks details on rate limits, output structure, or any nuances beyond the schema. With annotations present, this small addition warrants a mid-range score, but no contradiction exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three words cannot adequately describe a tool with 17 parameters and rich filtering options. While there is no redundancy, the text is under-specified; it sacrifices necessary detail for brevity.

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

Completeness1/5

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

For a complex screener with 17 parameters, a one-phrase description is completely inadequate. It does not explain what results look like, how filters work, or any prerequisites. The schema and annotations cover the data model, but the description itself fails to provide holistic context.

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?

All 17 parameters have descriptions in the schema, giving 100% coverage. The tool description itself mentions none of the parameters, but the schema fully documents them, so a baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Stock screener (paid)' essentially restates the tool's title with a parenthetical cost note. It lacks a verb and does not explain what the tool does (e.g., 'filters stocks by criteria'). This is a tautology rather than a functional description.

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?

No guidance is provided on when to use this tool versus any sibling tools like 'quote', 'search_symbol', or 'intraday'. The description only mentions that it is paid, which is a cost constraint, not a usage recommendation.

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

All Fmp toolsInspect
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