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

Financial Modeling Prep MCP Server

by imbenrabi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

getIndex1HourData

Read-onlyIdempotent

Retrieve 1-hour intraday price and volume data for stock indexes to track medium-term market trends during the trading day; specify symbol and optional date range.

Instructions

Access 1-hour interval intraday data for stock indexes using the Intraday 1-Hour Price Data API. This API provides detailed price movements and volume within hourly intervals, making it ideal for tracking medium-term market trends during the trading day.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>"
    },
    "name": "getIndex1HourData"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoEnd date (YYYY-MM-DD)
symbolYesIndex symbol (e.g., ^GSPC for S&P 500)
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.4/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 the payload contains price movements and volume per hourly interval, but says nothing about date-range behavior (defaults, maximum span), data limits, or symbol format handling.

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 sentences, front-loaded with the interval and resource. The second sentence's closing clause ('making it ideal for tracking medium-term market trends') is mild marketing filler, but the sentence still conveys payload content.

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?

For a three-parameter read tool with full schema coverage and annotations, the essentials are present, and the mention of price and volume partially compensates for the missing output schema. It still lacks any guidance on date-range limits or pagination/volume of returned rows, which an agent needs to call it safely.

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 symbol, from_date and to all documented including the '^GSPC' example and YYYY-MM-DD format, so the schema already does the work. The description adds no meaning about how the date range interacts with the interval or what happens if dates are omitted.

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?

States a specific verb and resource: 'Access 1-hour interval intraday data for stock indexes,' with the interval spelled out in the name and description. That interval specificity implicitly separates it from siblings like getIndex1MinuteData and getIndex5MinuteData, though no sibling is named explicitly.

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?

Offers only an implied use case ('ideal for tracking medium-term market trends during the trading day'). There is no statement of when to prefer the 1-hour interval over the 1-minute or 5-minute variants, and no prerequisites or exclusions.

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