Twelvedata

Eod

eod

Read-onlyIdempotent

Twelve Data end-of-day closing quote for a symbol. Returns the last closing price, volume, and date. Use for daily settlement prices rather than intraday data.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`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.
`exchange`	No	Optional exchange filter (e.g. "NASDAQ", "NYSE", "Binance").

Output Schema

TableJSON Schema

Name	Required	Description	Default
`close`	No
`symbol`	No
`currency`	No
`datetime`	No
`exchange`	No
`mic_code`	No
`timestamp`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields 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."

addedOutput schema / properties / close
```
Added value: +{
+  "type": "string"
+}
```

removedOutput schema / properties / code

Removed value: -{
-  "description": "Response code",
-  "type": "number"
-}

addedOutput schema / properties / currency
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / datetime
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / exchange
```
Added value: +{
+  "type": "string"
+}
```

removedOutput schema / properties / message

Removed value: -{
-  "description": "Response message",
-  "type": "string"
-}

addedOutput schema / properties / mic_code
```
Added value: +{
+  "type": "string"
+}
```

removedOutput schema / properties / status

Removed value: -{
-  "description": "Response status",
-  "type": "string"
-}

addedOutput schema / properties / symbol
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / timestamp
```
Added value: +{
+  "type": "number"
+}
```

Changed2 schema fields changedJun 24, 2026

addedInput schema / properties / exchange

Added value: +{
+  "description": "Optional exchange filter (e.g. \"NASDAQ\", \"NYSE\", \"Binance\").",
+  "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"
+}

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

Changed2 schema fields changedMay 22, 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"
+}

First observedMay 20, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior. The description adds useful context beyond those annotations by naming the data provider (Twelve Data), specifying the returned fields, and clarifying the daily-settlement scope, which is genuine behavioral information.

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 two tight sentences with no filler. It front-loads what the tool does and returns, then gives a brief usage direction. Every sentence contributes value.

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?

For a simple two-parameter tool with full schema coverage, rich annotations, and an output schema, the description covers the essential purpose, output content, data source, and intended use. Nothing critical is missing for an agent to select and invoke the tool correctly.

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 both parameters, including symbol formats, batch support, and exchange filtering. The description itself adds little parameter detail, but the baseline of 3 is appropriate because the schema carries the semantic burden.

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?

The description names a specific resource (end-of-day closing quote) and states what it returns (last closing price, volume, date). It also clarifies the tool's scope by distinguishing daily settlement data from intraday data, which helps separate it from siblings like time_series and price.

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 gives an explicit use case: 'Use for daily settlement prices rather than intraday data.' This clearly signals when the tool is appropriate and when it is not, though it does not name an alternative tool explicitly.

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.

Eod

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources