Skip to main content
Glama

fmp_fetch

Fetch financial data from any registered FMP endpoint, including income statements, balance sheets, stock prices, earnings calls, and SEC filings.

Instructions

Fetch data from any registered FMP endpoint.

This is the primary data fetching tool. Use fmp_list_endpoints to discover available endpoints, and fmp_describe to see required parameters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoFiling type filter (for sec_filings endpoint, e.g., "10-K", "10-Q").
yearNoFiscal year (for earnings_transcript endpoint).
limitNoMaximum number of records to return.
queryNoSearch query (for search endpoint).
outputNoOutput mode: inline records or CSV file path.inline
periodNoReporting period for financial statements ("annual" or "quarter").
symbolNoStock symbol (e.g., "AAPL", "MSFT"). Required for most endpoints.
columnsNoOptional columns filter as JSON array or comma-separated string.
quarterNoQuarter 1-4 (for earnings_transcript endpoint).
to_dateNoEnd date for price/rate data (YYYY-MM-DD format).
endpointYesName of the FMP endpoint. Common endpoints: - income_statement: Income statement data. `date` is period-end/as-of date. - balance_sheet: Balance sheet data. `date` is period-end/as-of date. - cash_flow: Cash flow statement data. `date` is period-end/as-of date. - key_metrics: Financial ratios and metrics. `date` is period-end/as-of date; `marketCap` is period-aligned, not current. - key_metrics_ttm: TTM metrics; FMP does not surface a period-end column. - historical_price_eod: Raw end-of-day prices and FX pair closes. For historical FX, use symbols such as USDTWD with from_date/to_date, then label basis as management_guidance_fx_assumption when guidance provides the FX rate or fmp_historical_fx_exact_date / fmp_historical_fx_previous_close when using FMP daily closes. - historical_price_adjusted: Adjusted stock prices - dividends: Dividend history - analyst_estimates: Analyst EPS/revenue estimates - price_target: Analyst price targets - earnings_transcript: Earnings call transcripts - sec_filings: SEC filing metadata
from_dateNoStart date for price/rate data (YYYY-MM-DD format).
use_cacheNoWhether to use cached data (default: True). Set False for fresh data.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

No annotations provided, so description carries full burden. It only says 'Fetch data' but does not disclose read-only nature, side effects, rate limits, error behavior, or any other behavioral traits. The minimal description leaves significant gaps.

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

Conciseness5/5

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

Two sentences, zero wasted words. Front-loaded with the core action and immediately provides usage guidance. Highly concise and structured.

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?

Despite 13 parameters and an output schema, the description is extremely brief. It does not explain how to construct queries, interpret results, or handle common scenarios. It relies too heavily on other tools and schema, making it incomplete for a primary tool.

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 baseline is 3. The description adds no extra meaning beyond the schema; it relies entirely on the schema for parameter details. The mention of fmp_describe is about discovery, not semantics.

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

Purpose5/5

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

Description clearly states 'Fetch data from any registered FMP endpoint' with a specific verb and resource. It distinguishes from sibling tools fmp_list_endpoints and fmp_describe by positioning itself as the primary fetching tool, which is explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly instructs to use fmp_list_endpoints for discovery and fmp_describe for parameters. Provides clear context for when to use this tool vs alternatives, though no explicit when-not scenarios are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/henrysouchien/fmp-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server