Twelvedata

Currency Conversion

currency_conversion

Read-onlyIdempotent

Twelve Data real-time currency conversion: pass a forex pair symbol (e.g. 'EUR/USD') and an amount to get the converted value at the current exchange rate.

Input Schema

TableJSON Schema

Name	Required	Description
`dp`	No	Decimal places (0–11).
`amount`	Yes	Amount in the base currency to convert.
`format`	No	Response format: "JSON" (default) or "CSV".
`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.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`rate`	No
`amount`	No
`symbol`	No
`timestamp`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 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 / amount
```
Added value: +{
+  "type": "number"
+}
```

removedOutput schema / properties / code

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

removedOutput schema / properties / message

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

addedOutput schema / properties / rate
```
Added value: +{
+  "type": "number"
+}
```

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"
+}
```

Changed4 schema fields changedJun 24, 2026

addedInput schema / properties / amount / description

Added value: +"Amount in the base currency to convert."

addedInput schema / properties / dp / description
```
Added value: +"Decimal places (0–11)."
```

addedInput schema / properties / format / description

Added value: +"Response format: \"JSON\" (default) or \"CSV\"."

addedInput schema / properties / symbol / description

Added 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\")."

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "amount": 100,
+    "symbol": "EUR/USD"
+  },
+  {
+    "amount": 50,
+    "dp": 2,
+    "symbol": "GBP/JPY"
+  }
+]

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

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior. The description adds useful context by noting the operation is real-time and uses the current exchange rate, but it does not disclose any further behavioral traits such as data delays, API-key restrictions, or batch behavior, which are only partially represented in the schema.

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 a single, front-loaded sentence with no filler. It immediately identifies the provider, the operation, the required inputs, and the expected result, making it easy for an agent to scan and act on.

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 read-only conversion tool, the description plus the fully documented schema and output schema provide enough to call it correctly. The main gap is the lack of sibling disambiguation and the disconnect between the description's narrow currency focus and the schema's broader symbol support, but structured fields compensate for most missing detail.

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 already documents symbol, amount, dp, and format. The description reiterates symbol and amount and gives a concrete example, but adds no meaning beyond the schema for dp or format. This meets the baseline but does not exceed it.

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: convert an amount from one currency to another using a forex pair like 'EUR/USD' at the current exchange rate. It is clear and actionable, but it does not differentiate this tool from siblings such as exchange_rate or quote, and the schema reveals broader symbol support (stocks, crypto, ETFs) that the description does not mention.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the use case: real-time currency conversion with a forex pair and an amount. However, it provides no explicit guidance about when not to use this tool, does not name alternatives like exchange_rate or price, and does not mention the broader ticker support visible in the schema.

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.