yfinance-ai MCP server

Overview Schema Source Related Servers Discussions Admin

get_balance_sheet

Read-onlyIdempotent

Retrieve a stock's annual or quarterly balance sheet by ticker, including assets, liabilities, and equity for financial analysis.

Instructions

Get balance sheet data.

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

Returns: Balance sheet with assets, liabilities, and equity

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_balance_sheet"
  }
}

Input Schema

Name	Required	Description	Default
`period`	No		annual
`ticker`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 21, 2026

TDQS

B3/5.0

Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered and the description adds nothing behavioral on top. It does not mention data freshness, rate limits, or whether a missing ticker fails or returns empty.

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

Conciseness3/5

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

Front-loaded with the purpose, which is good, but the Args and Returns blocks largely restate the input schema and the declared output schema. Acceptable but not tightly written.

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?

An output schema exists, so omitting return detail is fine, and both parameters are explained. What is missing for a two-parameter financial-statement tool in a very crowded sibling set is any indication of when to reach for this tool versus the many other financial data tools.

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 carries the full burden and does document both parameters: ticker as a stock ticker symbol and period as 'annual' or 'quarterly'. The period values are the only place the allowed values appear, since the schema has a default but no enum constraint.

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 and resource ('Get balance sheet data'), which clearly separates it from siblings like get_income_statement and get_cash_flow. However, it never names those siblings or otherwise distinguishes itself beyond the resource noun.

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 prerequisites, and no mention of alternatives such as get_ttm_financials or get_financial_summary. With ~70 sibling tools, the agent gets no routing help.

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

Deploy Server