Skip to main content
Glama
Financial Modeling Prep MCP Server

Financial Modeling Prep MCP Server

getBiggestLosers

Read-onlyIdempotent

Access data on stocks with significant price drops to identify declining companies and track downward market movers.

Instructions

Access data on the stocks with the largest price drops using the Biggest Stock Losers API. Identify companies experiencing significant declines and track the stocks that are falling the fastest in the market.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field 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"
  2. Changed1 schema field changedv1.0.0
    • removedInput schema / additionalProperties
      Removed value: -false
  3. 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, openWorldHint, and idempotentHint, so the safety profile is covered. The description adds no behavioral context of its own: no data freshness (intraday vs end-of-day), no market/exchange coverage, no indication of how many losers are returned or whether results are ranked by percentage or absolute drop.

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

Conciseness3/5

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

Two sentences, the second of which largely repeats the first ('significant declines' / 'falling the fastest'), padding rather than adding information. The core purpose is front-loaded, but the space could have carried the missing scope details instead.

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?

With no output schema and no parameters, the description is the only source of truth about what comes back, yet it never says what a result contains (symbol, price, change percent, volume) or over what time window the 'largest drops' are measured. For a data-retrieval tool with no structured fallback, that leaves the agent guessing at result shape and freshness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4 and there is nothing for the description to compensate for. The schema is empty and fully covered.

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 clearly states a verb and resource: retrieve data on stocks with the largest price drops. An agent can tell this is a market-mover listing rather than a per-symbol quote. However, it never distinguishes itself from close siblings such as getBiggestGainers, getMostActiveStocks, or stockScreener, and the second sentence mostly restates the first.

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?

There is no guidance on when to use this versus alternatives, despite several near-neighbors in the sibling list (gainers, most active, screener). Nothing says whether this is a daily snapshot, real-time, or scoped to a particular exchange or market, which is exactly the information needed to choose it confidently.

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