TipRanks

get_stock_splits

Read-onlyIdempotent

Returns the stock-split calendar with split ratios and direction (Forward / Reverse). Use for upcoming splits, reverse-split alerts, historical split lookup.

Args:
    fromDate: Start date YYYY-MM-DD (default: 30 days ago)
    toDate: End date YYYY-MM-DD (default: 30 days from now)
    type: Optional filter — 'Forward' or 'Reverse' (case-insensitive).
          Empty string returns both.
    limit: Max rows (default: 25, max: 100)
    ticker: Optional single symbol. Widen fromDate to search a company's history —
            the default window is only today ± 30 days.

Returns: { totalCount, data: [{ ticker, companyName, effectiveDate, type,
                                splitRatio, splitRatioText }] }. A filtered call
         (ticker or type) also returns `matched` and `window`: `totalCount` is
         every split in the window, `matched` how many passed the filter. The
         window is read in full before filtering, so an empty result means there
         genuinely are none rather than that the first page held none.

Input Schema

TableJSON Schema

Name	Required	Description
`type`	No	Optional filter: 'Forward' or 'Reverse' (case-insensitive); omit to return both.
`limit`	No
`ticker`	No	Optional. Return only this company's splits within the window, e.g. 'NVDA'. Pair with a wide fromDate for 'has X ever split'.
`toDate`	No
`fromDate`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 28, 2026

addedInput schema / properties / ticker

Added value: +{
+  "default": "",
+  "description": "Optional. Return only this company's splits within the window, e.g. 'NVDA'. Pair with a wide fromDate for 'has X ever split'.",
+  "title": "Ticker",
+  "type": "string"
+}

Changed1 schema field changedAug 17, 2026

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "get_stock_splitsOutput",
-  "type": "object"
-}New value: +null

First observedJul 21, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already mark this as read-only, idempotent, and non-destructive, and the description adds substantial behavioral context beyond them: default date windows, limit cap, ticker caveat, and the important detail that the window is read in full before filtering so an empty result is meaningful. No contradiction exists.

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 front-loaded with purpose and use cases, followed by a clean Args block and a returns explanation. The length is justified by the tool's filtering semantics and low schema coverage; every sentence contributes actionable information rather than padding.

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

Completeness5/5

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

With no output schema and sparse input schema, the description supplies a complete invocation picture: defaults, filters, max rows, return object shape, and interpretation of filtered results. Nothing an agent needs to call this correctly or interpret its response is missing.

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

Parameters5/5

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

Schema coverage is only 40%, so the description must compensate — and it does completely. It documents every parameter with format, defaults, and behavior, including YYYY-MM-DD formats, default date ranges, type case-insensitivity, limit range, and ticker-specific guidance about widening fromDate. This adds real meaning beyond the sparse schema.

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 opens with a specific verb and resource: returns the stock-split calendar with split ratios and direction (Forward / Reverse). It also names concrete use cases — upcoming splits, reverse-split alerts, historical lookup — which clearly distinguishes it from calendar-like sibling tools.

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?

The description states explicit use cases ('Use for upcoming splits, reverse-split alerts, historical split lookup'), giving an agent clear context for when to invoke it. It does not explicitly state when not to use it or name alternatives, so it misses the higher bar of exclusion guidance.

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

All TipRanks tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?