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

Financial Modeling Prep MCP Server

by imbenrabi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

getForexHistoricalFullChart

Read-onlyIdempotent

Retrieve end-of-day historical forex data for a currency pair, including OHLC, volume, and percentage changes, to analyze price movements over a selected date range.

Instructions

Access comprehensive historical end-of-day forex price data with the Full Historical Forex Chart API. Gain detailed insights into currency pair movements, including open, high, low, close (OHLC) prices, volume, and percentage changes.

Input Schema

NameRequiredDescriptionDefault
toNoEnd date (YYYY-MM-DD)
symbolYesForex pair symbol (e.g., EURUSD)
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 the end-of-day granularity and the field set returned, which is useful context. It says nothing about date-range limits, defaults, maximum span, or pagination behavior for a historical data endpoint.

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, but the second is largely marketing filler ('Gain detailed insights into currency pair movements') that partially restates the first. The field list (OHLC, volume, percentage changes) earns its place; the framing around it does not.

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?

No output schema exists, so the description must convey return shape, and it does list OHLC, volume and percentage change. For a historical time-series endpoint, though, an agent still lacks essentials: default date range, maximum span, and how this differs from the Light Chart variant.

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 symbol, from_date and to with YYYY-MM-DD formats are fully documented in the schema. The description adds no meaning beyond that, so baseline 3 applies. It could have clarified defaults when dates are omitted, which the schema does not say either.

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 names the resource precisely: historical end-of-day forex price data with OHLC, volume and percentage change. However, it does not distinguish this from the sibling getForexHistoricalLightChart, which presumably returns a reduced field set, so an agent cannot tell which one to pick from the description alone.

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?

No when-to-use guidance and no mention of when NOT to use it. With a near-identical sibling (getForexHistoricalLightChart) in the same family, the absence of any routing hint is a real gap. The only implied usage is 'you want historical forex data'.

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