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

Financial Modeling Prep MCP Server

by imbenrabi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

searchForexNews

Read-onlyIdempotent

Search foreign exchange news by currency pair symbols and optional date range to find targeted updates for specific forex markets.

Instructions

Search for foreign exchange news using the FMP Search Forex News API. Find targeted news on specific currency pairs by entering their symbols for focused updates.

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 forex pairs
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

A3.5/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 only that results are symbol-targeted news; it says nothing about pagination depth, default 20/max 250 limits, or freshness/ordering of results, which are the traits an agent would actually want beyond the annotations.

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 with the actionable part (symbol-scoped targeted news) up front. The opening clause 'using the FMP Search Forex News API' is redundant with the tool name and earns little, but there is no bloat beyond that.

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

Completeness4/5

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

For a five-parameter, read-only news search with full schema coverage and no output schema, the definition covers what it returns conceptually (targeted forex news per pair) and the schema handles dates and paging. The remaining gap is sibling differentiation, not missing call mechanics.

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 all five parameters (symbols, from_date, to_date, page, limit) are documented in the schema including comma-separated symbol format and the limit default/max. The description restates only the symbols parameter at a high level, adding no example pair format (e.g. EURUSD) or date-window guidance.

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?

State a clear verb+resource: search forex news, targeted by currency pair symbols. It does not, however, distinguish itself from the sibling getForexNews (latest forex news) or searchStockNews/searchCryptoNews, leaving the agent to infer the difference between 'search by symbol' and 'get latest'.

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?

The phrase 'Find targeted news on specific currency pairs by entering their symbols' implies the use case (symbol-scoped news lookups), but it never states when to choose this over getForexNews or the other search* news siblings, and gives no exclusions or prerequisites.

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