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

Financial Modeling Prep MCP Server

by imbenrabi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

searchPressReleases

Read-onlyIdempotent

Find corporate announcements and updates by stock symbols, with optional date filters, to track company news and disclosures.

Instructions

Search for company press releases with the FMP Search Press Releases API. Find specific corporate announcements and updates by entering a stock symbol or company name.

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. The description adds the search-by-symbol framing but omits behavior an agent would want: pagination defaults, the 250-result cap, the date-range scoping, and whether coverage spans all history or recent filings only.

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 action and resource. The second sentence partially repeats the first ('find ... announcements' vs 'search ... press releases') and the vendor API name is low-value, but nothing is verbose enough to hurt comprehension.

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?

With no output schema, the description carries the burden of telling the agent what comes back, and it does not — no mention of headline, publish date, text or source URL. It also omits the multi-symbol comma-separated behavior and date filtering, leaving an agent to infer the shape of results 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 the from_date, to, page and limit parameters are already documented in the schema and the baseline of 3 applies. The description adds nothing about date-range combination or pagination, and stating 'company name' as an input is misleading since the symbols parameter accepts comma-separated tickers only.

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 ('Search for company press releases') and names the underlying API, so the retrieval target is unambiguous. However, it never distinguishes itself from the sibling getPressReleases, which an agent must choose between, and the mention of 'company name' conflicts with the symbol-only search semantics.

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: 'Find specific corporate announcements and updates by entering a stock symbol' suggests targeted lookups rather than browsing. There is no explicit when-to-use/when-not, no mention of when getPressReleases or searchStockNews would be preferable, and no note that a symbol is mandatory.

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