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

Financial Modeling Prep MCP Server

by imbenrabi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

getFinancialStatementGrowth

Read-onlyIdempotent

Analyze growth of key income, balance sheet, and cash flow statement items by stock symbol to track financial performance trends over time.

Instructions

Analyze the growth of key financial statement items across income, balance sheet, and cash flow statements with the Financial Statement Growth API. Track changes over time to understand trends in financial performance.

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": "getFinancialStatementGrowth"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoLimit on number of results (default: 100, max: 1000)
periodNoPeriod (Q1, Q2, Q3, Q4, or FY)
symbolYesStock symbol

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. First observed

TDQS

B3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, and the description adds no behavior beyond them — no note on how many periods are returned, whether growth is annual or quarterly, units of the growth figures, or how the symbol universe is resolved. With annotations covering the safety profile, the remaining behavioral questions an agent would have go unanswered.

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 core capability and no redundant phrasing. The second sentence leans toward marketing filler ('understand trends in financial performance') but is short enough not to be costly.

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-only tool with full schema coverage, the description covers the basic purpose but omits anything about the shape or scale of the result (no output schema exists), which matters for an aggregation tool spanning three statements and multiple periods.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so symbol, period and limit are already documented in the schema. The description mentions the three statement types but does not tie them to parameters or clarify period behavior (e.g., whether FY vs Q1–Q4 changes the number of rows returned), so it adds essentially nothing beyond the schema.

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?

Names a specific verb (analyze growth) and a specific resource (key financial statement items across income, balance sheet and cash flow statements). However it never distinguishes itself from the closely related siblings getIncomeStatementGrowth, getBalanceSheetStatementGrowth and getCashFlowStatementGrowth, so an agent must infer that this one aggregates all three.

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?

The phrase 'Track changes over time to understand trends in financial performance' implies a trend-analysis use case, but there is no explicit when-to-use, when-not-to-use, or pointer to the per-statement growth tools as an alternative when only one statement is needed.

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