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

Financial Modeling Prep MCP Server

by imbenrabi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

getHistoricalIndustryPerformance

Read-onlyIdempotent

Retrieve historical performance data for a specific industry to track long-term trends and analyze how industries evolved across exchanges over time.

Instructions

Access historical performance data for industries using the Historical Industry Performance API. Track long-term trends and analyze how different industries have evolved over time across various stock exchanges.

Input Schema

NameRequiredDescriptionDefault
toNoEnd date (YYYY-MM-DD)
exchangeNoExchange (e.g., NASDAQ)
industryYesIndustry (e.g., Biotechnology)
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

C2.5/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly, idempotent, and openWorld, so safety is covered. The description adds only vague framing ('track long-term trends', 'have evolved over time') without disclosing return shape, granularity (daily/monthly), pagination, or how missing dates behave — none of which the annotations cover.

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 short sentences, but the second ('Track long-term trends and analyze how different industries have evolved over time') is unfalsifiable marketing filler that occupies half the text without conveying callable information.

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

Completeness2/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 bears responsibility for telling the agent what comes back — a time series? per-exchange rows? — and it does not. Combined with no differentiation from nearest siblings, an agent cannot confidently decide to call this over the snapshot or summary variants.

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%, so every parameter (from_date, to, exchange, industry) is already documented with examples and formats. The description only echoes 'across various stock exchanges', adding no semantics beyond the schema. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a verb and resource ('Access historical performance data for industries') but 'performance' is undefined — it could mean price returns, market cap, or index values. Nothing distinguishes it from getIndustryPerformanceSnapshot or getIndustryPerformanceSummary, both of which sound like the same resource.

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 at all. With siblings like getIndustryPerformanceSnapshot, getHistoricalSectorPerformance, and getHistoricalIndustryPE, the description should say which question this answers (e.g., time series of industry-level performance vs. point-in-time snapshot), but it offers none.

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