Skip to main content
Glama
Sign In
yfinance-ai MCP server

yfinance-ai MCP server

by lkcair
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_cash_flow

Read-onlyIdempotent

Retrieve a company's annual or quarterly cash flow statement by ticker to review operating, investing, and financing activities.

Instructions

Get cash flow statement data.

Args: ticker: Stock ticker symbol period: 'annual' or 'quarterly'

Returns: Cash flow statement with operating, investing, and financing activities

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": {
      "ticker": "<ticker>"
    },
    "name": "get_cash_flow"
  }
}

Input Schema

NameRequiredDescriptionDefault
periodNoannual
tickerYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered structurally. The description adds only the shape of the result (operating/investing/financing sections) and says nothing about data freshness, data source, or error/empty behavior, so it clears the lower annotated bar without being rich.

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?

Front-loaded with the purpose, then compact Args/Returns blocks with zero filler. Every line earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present and annotations covering safety, the description only needs to orient the caller, which it does adequately for a read-only financial fetch. It stops short of noting the default period or any data-scope caveats, but nothing critical is missing.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must carry the parameter burden, and it does: ticker is defined as a stock ticker symbol and period is given its allowed values 'annual' or 'quarterly'. The only omission is that the default period (annual, per the schema) and casing/normalization rules are not restated.

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 ('Get cash flow statement data') and names the three cash-flow sections returned. It's clearly distinguishable from get_balance_sheet and get_income_statement by the resource name alone, but the description never acknowledges those siblings or contrasts itself with them.

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, no mention of when to prefer get_ttm_financials/get_financial_summary, and no stated prerequisites. The agent is left to infer everything about routing from the tool name.

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