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

Financial Modeling Prep MCP Server

by imbenrabi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

searchStockNews

Read-onlyIdempotent

Search stock-related news by ticker symbol or company name and filter by date to track company developments.

Instructions

Search for stock-related news using the FMP Search Stock News API. Find specific stock news by entering a ticker symbol or company name to track the latest developments.

Input Schema

NameRequiredDescriptionDefault
toNoEnd date (YYYY-MM-DD)
pageNoPage number (default: 0)
limitNoLimit on number of results (default: 20, max: 250)
symbolsYesComma-separated list of stock symbols
from_dateNoStart date (YYYY-MM-DD)

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. Changed2 schema fields changedv2.6.10
    • removedInput schema / properties / from
      Removed value: -{
-  "description": "Start date (YYYY-MM-DD)",
-  "type": "string"
-}
    • addedInput schema / properties / from_date
      Added value: +{
+  "description": "Start date (YYYY-MM-DD)",
+  "type": "string"
+}
  3. First observed

TDQS

B3.4/5.0
Behavior3/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 for free. The description adds only that results come from an external FMP API and are scoped to a ticker; it says nothing about result volume, pagination behavior, or how pagination interacts with the limit cap.

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 short sentences, front-loaded with the verb and resource, with no filler. The second sentence is partly redundant with the first ("Find specific stock news" restates "Search for stock-related news"), which keeps it out of the top band.

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?

A read-only search with full schema coverage and no output schema needs only modest description, and this covers the core use case. It is still incomplete for an agent that must choose among many news endpoints, and it omits any hint that results can be paginated or date-bounded.

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 the baseline is 3. The description restates the `symbols` parameter as "a ticker symbol or company name", which actually goes slightly beyond the schema wording (comma-separated symbols) and could mislead an agent into passing a company name; it says nothing about the from_date/to date-range parameters.

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?

Names a specific verb and resource ("search stock news") plus the underlying API, and says it targets a specific ticker rather than a general news feed. It does not differentiate itself from the closely related sibling getStockNews, so an agent cannot tell from the description alone which news endpoint to pick.

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 only implied by "track the latest developments" — there is no explicit statement of when to use this versus getStockNews, getGeneralNews, or searchPressReleases, all of which appear in the sibling list. No prerequisites, no guidance on batching multiple symbols, and no note about date filtering are given.

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