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

yfinance-ai MCP server

by lkcair
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_stock_splits

Read-onlyIdempotent

Retrieve complete stock split history for a ticker symbol, including split dates and ratios, to track corporate actions and adjust historical price analysis.

Instructions

Get stock split history.

Args: ticker: Stock ticker symbol

Returns: Complete stock split history with dates and ratios

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

Input Schema

NameRequiredDescriptionDefault
tickerYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive, open-world operation. The description adds that the result is a complete split history with dates and ratios, which is useful return-context but does not add deeper behavioral details such as data source or rate limits.

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 short, front-loaded, and structured with Args and Returns sections. Every line contributes directly to understanding the tool without wasted prose.

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?

For a simple one-parameter lookup tool with rich annotations and an output schema, the description is nearly complete. Its main gap is the lack of sibling differentiation, especially relative to get_splits_calendar.

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 0%, so the description must compensate. It does identify the sole parameter as 'ticker: Stock ticker symbol,' but it does not add format examples, exchange conventions, or validation details beyond the obvious meaning.

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 stock split history.' It is clear what the tool does, but it does not distinguish itself from potentially overlapping siblings such as get_splits_calendar or get_corporate_actions.

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?

The description gives no explicit when-to-use guidance, prerequisites, or alternatives. Usage is only implied by the tool name and purpose, with no routing advice for related tools.

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