Skip to main content
Glama
imbenrabi

Financial Modeling Prep MCP Server

by imbenrabi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

getEconomicIndicators

Read-onlyIdempotent

Access real-time and historical economic data for key indicators like GDP, unemployment, and inflation with the FMP Economic Indicators API. Use this data to measure economic performance and identify growth trends.

Instructions

Access real-time and historical economic data for key indicators like GDP, unemployment, and inflation with the FMP Economic Indicators API. Use this data to measure economic performance and identify growth trends.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoOptional end date (YYYY-MM-DD); the date range can span at most 90 days
nameYesIndicator name, e.g. GDP, realGDP, nominalPotentialGDP, realGDPPerCapita, federalFunds, CPI, inflationRate, inflation, retailSales, consumerSentiment, durableGoods, unemploymentRate, totalNonfarmPayroll, initialClaims, industrialProductionTotalIndex, newPrivatelyOwnedHousingUnitsStartedTotalUnits, totalVehicleSales, retailMoneyFunds, smoothedUSRecessionProbabilities, 3MonthOr90DayRatesAndYieldsCertificatesOfDeposit, commercialBankInterestRateOnCreditCardPlansAllAccounts, 30YearFixedRateMortgageAverage, 15YearFixedRateMortgageAverage, tradeBalanceGoodsAndServices
from_dateNoOptional start date (YYYY-MM-DD); the date range can span at most 90 days

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.8.0
    • changedInput schema / properties / from_date / description
      Previous value: -"Optional start date (YYYY-MM-DD)"New value: +"Optional start date (YYYY-MM-DD); the date range can span at most 90 days"
    • changedInput schema / properties / name / description
      Previous value: -"Name of the indicator"New value: +"Indicator name, e.g. GDP, realGDP, nominalPotentialGDP, realGDPPerCapita, federalFunds, CPI, inflationRate, inflation, retailSales, consumerSentiment, durableGoods, unemploymentRate, totalNonfarmPayroll, initialClaims, industrialProductionTotalIndex, newPrivatelyOwnedHousingUnitsStartedTotalUnits, totalVehicleSales, retailMoneyFunds, smoothedUSRecessionProbabilities, 3MonthOr90DayRatesAndYieldsCertificatesOfDeposit, commercialBankInterestRateOnCreditCardPlansAllAccounts, 30YearFixedRateMortgageAverage, 15YearFixedRateMortgageAverage, tradeBalanceGoodsAndServices"
    • changedInput schema / properties / to / description
      Previous value: -"Optional end date (YYYY-MM-DD)"New value: +"Optional end date (YYYY-MM-DD); the date range can span at most 90 days"
  2. Changed2 schema fields changedv2.6.10
    • removedInput schema / properties / from
      Removed value: -{
-  "description": "Optional start date (YYYY-MM-DD)",
-  "type": "string"
-}
    • addedInput schema / properties / from_date
      Added value: +{
+  "description": "Optional 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 and idempotency profile is covered. The description adds the useful fact that both real-time and historical data are available, but says nothing about source latency, rate limits, or the 90-day window limit that governs a call.

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?

The first sentence is appropriately front-loaded and informative, but the second sentence ('Use this data to measure economic performance and identify growth trends') is marketing filler that earns no place in a tool contract. The vendor branding ('with the FMP Economic Indicators API') is also low-value padding.

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 and a fully documented parameter set, the description's main remaining job is to convey what a call yields. It notes real-time and historical coverage, which is useful, but omits that results are time-series observations per indicator and gives no sense of response shape, leaving the agent with an adequate but thin picture.

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%: the name, to, and from_date parameters are all documented in the schema itself, including the comprehensive indicator list and the 90-day maximum span. The description repeats the GDP/unemployment/inflation examples already present in the name field and adds no syntax or semantics beyond that, 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 names a specific verb (access) and resource (real-time and historical economic data) with concrete examples (GDP, unemployment, inflation), so an agent immediately knows what the tool returns. It does not, however, distinguish itself from closely related siblings such as getEconomicCalendar, getTreasuryRates, or getMarketRiskPremium, nor does it clarify the indicator-series nature of the data.

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?

The only usage statement is 'Use this data to measure economic performance and identify growth trends,' which is generic motivation rather than invocation guidance. There is no indication of when to prefer this tool over the economic-calendar or treasury-rate siblings, and no mention of the 90-day range constraint as a practical limitation.

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