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

Financial Modeling Prep MCP Server

by imbenrabi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

getKeyMetricsTTM

Read-onlyIdempotent

Retrieve trailing twelve-month key performance metrics for a stock symbol to analyze profitability, capital efficiency, liquidity, and overall financial health.

Instructions

Retrieve a comprehensive set of trailing twelve-month (TTM) key performance metrics with the TTM Key Metrics API. Access data related to a company's profitability, capital efficiency, and liquidity, allowing for detailed analysis of its financial health over the past year.

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

Input Schema

NameRequiredDescriptionDefault
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.2/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 carried by structured data. The description adds useful scope about what the returned metrics represent (trailing twelve months across profitability, capital efficiency, liquidity) but says nothing about units, currency, handling of companies without full TTM history, or whether missing metrics are omitted or null.

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 action and resource, which is the right shape. Some words are promotional filler ('comprehensive set', 'allowing for detailed analysis of its financial health over the past year') that restate the value proposition rather than adding information an agent can act on.

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 one-parameter read tool with rich annotations and full schema coverage, this is adequate but thin. With no output schema present, the description could have said what the payload looks like (flat metric key/value set per symbol, date/fiscal period context), and it omits sibling disambiguation, which is the main thing an agent needs here.

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?

With a single parameter and 100% schema description coverage, the schema already documents 'symbol' fully, so the baseline of 3 applies. The description does not mention the symbol argument, its format (ticker vs exchange-qualified), or how invalid symbols behave, so it adds no meaning 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?

The description gives a specific verb (retrieve) and resource (TTM key performance metrics), and even enumerates the metric families covered (profitability, capital efficiency, liquidity). However, it never distinguishes itself from close siblings such as getKeyMetrics (non-TTM), getFinancialRatiosTTM, or getKeyMetricsTTMBulk, so an agent scanning the sibling list gets no help choosing this one over those.

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: nothing says to pick this over getKeyMetrics for annual figures or over getKeyMetricsTTMBulk for multi-symbol pulls. The only hint is the implied analyst use case ('allowing for detailed analysis of its financial health'), which does not select between alternatives or state prerequisites such as a valid listing symbol.

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