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

Financial Modeling Prep MCP Server

by imbenrabi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

getForexNews

Read-onlyIdempotent

Retrieve forex news articles by date range to access headlines, snippets, and publication URLs for market insights.

Instructions

Stay updated with the latest forex news articles from various sources using the FMP Forex News API. Access headlines, snippets, and publication URLs for comprehensive market insights.

Input Schema

NameRequiredDescriptionDefault
toNoEnd date (YYYY-MM-DD)
pageNoPage number (default: 0)
limitNoLimit on number of results (default: 20, max: 250)
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.1/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 that results come 'from various sources' and enumerates returned fields (headlines, snippets, URLs), which is genuinely useful given there is no output schema, but it does not describe pagination, ordering, or default time window behavior.

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?

Only two sentences and the purpose is front-loaded, but 'Stay updated with...' and 'for comprehensive market insights' are promotional filler, and 'using the FMP Forex News API' conveys nothing an agent can act on.

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?

Listing the returned fields compensates for the missing output schema, but for a four-parameter, paginated news endpoint the description says nothing about how date filters and paging interact or how results are ordered. It is adequate but leaves meaningful gaps.

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 coverage is 100%, with each of the four parameters (to, from_date, page, limit) documented including formats and defaults. The description adds no meaning beyond the schema and never even hints at date-range filtering or paging, so the baseline 3 applies.

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 states a specific resource and action: retrieving 'forex news articles' including headlines, snippets, and URLs. It is clearly distinguishable from the chart/quote siblings, but it never distinguishes itself from searchForexNews, which sits right next to it in the tool family.

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?

'Stay updated with the latest' hints at a current-news use case, but there is no explicit when-to-use guidance and no mention of searchForexNews as the alternative for keyword/symbol-filtered queries. An agent has to infer the routing decision from the name alone.

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