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

Financial Modeling Prep MCP Server

by imbenrabi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

getIncomeStatementTTM

Read-onlyIdempotent

Fetch trailing twelve-month income statement figures for a stock symbol to analyze profitability, compare competitors, and identify business trends.

Instructions

Access real-time income statement data for public companies, private companies, and ETFs with the FMP Real-Time Income Statements API. Track profitability, compare competitors, and identify business trends with up-to-date financial data.

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

Input Schema

NameRequiredDescriptionDefault
limitNoLimit on number of results (default: 100, max: 1000)
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

C2.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety and repeatability are covered structurally. The description adds no behavioral context beyond marketing copy: it does not clarify what TTM window is returned, whether data is a snapshot or rolling, how many periods come back, or what the limit parameter governs in practice.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, but the second is pure marketing ("Track profitability, compare competitors, and identify business trends with up-to-date financial data") and consumes space without informing invocation. Worse, the front-loaded claim ("real-time") is the wrong framing for a TTM endpoint, so the structure prioritizes promotion over the one fact that matters.

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?

The tool is simple — one required symbol, one optional limit, no output schema, annotations present — so the description does not need to explain return values. Still, given a large sibling family of income-statement variants (getIncomeStatement, getIncomeStatementGrowth, getIncomeStatementsBulk, getCashFlowStatementTTM), the description is incomplete in not identifying what makes the TTM variant distinct.

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 both parameters (symbol, limit with default 100 / max 1000) are already fully documented in the schema. The description adds nothing about either parameter, so the 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?

The description states a verb and resource ("Access ... income statement data") and lists coverage (public companies, private companies, ETFs). However, it never explains "TTM" (trailing twelve months) despite that being the defining trait in the tool name, and it uses "real-time" instead, which signals a different thing. It also gives no basis for choosing it over siblings like getIncomeStatement or getIncomeStatementGrowth.

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?

There is no when-to-use guidance at all — no conditions, prerequisites, or named alternatives. The promotional phrasing ("compare competitors", "identify business trends") describes analyst outcomes, not invocation criteria, so an agent learns nothing about when this tool beats getIncomeStatement or getIncomeStatementsBulk.

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