Skip to main content
Glama
maxscheijen

MCP Yahoo Finance

by maxscheijen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_cashflow

Retrieve a stock's cash flow statement by symbol and frequency from Yahoo Finance data. Use it to analyze operating, investing, and financing cash flows.

Instructions

Get the cashflow statement for a given stock symbol.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
freqNoStatement frequency. Defaults to "yearly".yearly
symbolYesStock symbol in Yahoo Finance format.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.2.0
    • addedInput schema / properties / freq / default
      Added value: +"yearly"
    • changedInput schema / properties / freq / description
      Previous value: -"At what frequency to get cashflow statements. Defaults to \"yearly\". Valid freqencies: \"yearly\", \"quarterly\", \"trainling\""New value: +"Statement frequency. Defaults to \"yearly\"."
    • addedInput schema / properties / freq / enum
      Added value: +[
+  "yearly",
+  "quarterly",
+  "trailing"
+]
  2. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It does not state whether the operation is read-only, what the return format is, what permissions are required, or how the data is sourced. It only asserts that a cashflow statement is returned.

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?

The description is a single efficient sentence with no redundant or filler content. The core purpose is front-loaded, making it easy to parse quickly.

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 input schema is complete and self-documenting, which covers parameter semantics. However, with no annotations and no output schema, the description does not clarify basic behavioral or return-value expectations for a financial data retrieval 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 both parameters are well documented in the schema, including the 'freq' enum and its default. The description adds no parameter meaning beyond the schema, so the baseline of 3 applies.

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 states a specific verb ('Get') and resource ('cashflow statement') and identifies the required input ('stock symbol'). It distinguishes the tool from siblings like get_income_statement by resource, though it does not explicitly differentiate among statement types.

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 guidance on when to use this tool versus alternatives such as get_income_statement or get_dividends, nor any prerequisites or exclusions. Usage is only implied by the resource 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