Twelvedata

Splits

splits

Read-onlyIdempotent

Twelve Data historical stock splits for a symbol: ratio, date. Use to adjust historical Twelve Data prices across split events.

Input Schema

TableJSON Schema

Name	Required	Description
`symbol`	Yes	Ticker/symbol. Stocks e.g. "AAPL", "MSFT"; forex "EUR/USD"; crypto "BTC/USD"; ETFs "SPY". Comma-separate for a batch (e.g. "AAPL,MSFT"). Market indices (SPX, N225, …) need a Grow-or-higher Twelve Data key passed via _apiKey — the shared key cannot quote them.
`end_date`	No	Optional end of range, "YYYY-MM-DD" or "YYYY-MM-DD HH:MM:SS".
`exchange`	No	Optional exchange filter (e.g. "NASDAQ", "NYSE", "Binance").
`start_date`	No	Optional start of range, "YYYY-MM-DD" or "YYYY-MM-DD HH:MM:SS".

Output Schema

TableJSON Schema

Name	Required	Description
`code`	No	Response code
`status`	No	Response status
`message`	No	Response message

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026

changedInput schema / properties / symbol / description

Previous value: -"Ticker/symbol. Stocks e.g. \"AAPL\", \"MSFT\"; forex \"EUR/USD\"; crypto \"BTC/USD\"; ETFs \"SPY\"; indices \"IXIC\". Comma-separate for a batch (e.g. \"AAPL,MSFT\")."New value: +"Ticker/symbol. Stocks e.g. \"AAPL\", \"MSFT\"; forex \"EUR/USD\"; crypto \"BTC/USD\"; ETFs \"SPY\". Comma-separate for a batch (e.g. \"AAPL,MSFT\"). Market indices (SPX, N225, …) need a Grow-or-higher Twelve Data key passed via _apiKey — the shared key cannot quote them."

Changed4 schema fields changedJun 24, 2026

addedInput schema / properties / end_date

Added value: +{
+  "description": "Optional end of range, \"YYYY-MM-DD\" or \"YYYY-MM-DD HH:MM:SS\".",
+  "type": "string"
+}

addedInput schema / properties / exchange

Added value: +{
+  "description": "Optional exchange filter (e.g. \"NASDAQ\", \"NYSE\", \"Binance\").",
+  "type": "string"
+}

addedInput schema / properties / start_date

Added value: +{
+  "description": "Optional start of range, \"YYYY-MM-DD\" or \"YYYY-MM-DD HH:MM:SS\".",
+  "type": "string"
+}

addedInput schema / properties / symbol

Added value: +{
+  "description": "Ticker/symbol. Stocks e.g. \"AAPL\", \"MSFT\"; forex \"EUR/USD\"; crypto \"BTC/USD\"; ETFs \"SPY\"; indices \"IXIC\". Comma-separate for a batch (e.g. \"AAPL,MSFT\").",
+  "type": "string"
+}

Changed2 schema fields changedMay 24, 2026

addedInput schema / examples

Added value: +[
+  {
+    "symbol": "AAPL"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "code": {
+      "description": "Response code",
+      "type": "number"
+    },
+    "message": {
+      "description": "Response message",
+      "type": "string"
+    },
+    "status": {
+      "description": "Response status",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedMay 24, 2026
- removedInput schema / additionalProperties
```
Removed value: -true
```
First observedMay 20, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare the tool read-only, idempotent, and non-destructive. The description adds that the data consists of split ratio/date history and frames it as an input for price adjustment, but it does not disclose further behavioral details such as defaults, limits, or edge cases—adequate given the annotations.

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?

Two short, front-loaded sentences with no filler. It states the resource, the output fields, and the use case in minimal words, making it easy for an agent to parse quickly.

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 a full output schema, fully described parameters, and safety annotations, the description only needs to state the tool's purpose and intended use, which it does. Nothing essential is missing for selecting and calling this simple historical data 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 the schema fully documents the symbol, date range, and exchange parameters. The description adds no additional parameter semantics beyond implying symbol-level lookup, so the baseline score of 3 is appropriate.

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 operation—returning historical stock splits for a symbol—and names the core fields (ratio, date). It is clear and distinct from corporate-action siblings like dividends or earnings, though it does not explicitly contrast itself with those alternatives.

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?

It gives an explicit intended use: 'Use to adjust historical Twelve Data prices across split events.' This provides actionable context for when to select the tool, but it does not mention exclusions or name alternatives such as price/time_series, so it stops short of a 5.

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

All Twelvedata 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.