Skip to main content
Glama
sherajdev

Twelve Data MCP Server

by sherajdev

Convert Currency

twelvedata_convert_currency
Read-onlyIdempotent

Convert currency amounts using real-time exchange rates. Supports fiat, precious metals like gold, and cryptocurrencies.

Instructions

Convert an amount from one currency to another using real-time rates.

Supports fiat currencies, precious metals (XAU, XAG), and cryptocurrencies.

Args:

  • from (string): Source currency code (e.g., "USD", "EUR", "XAU", "BTC")

  • to (string): Target currency code

  • amount (number): Amount to convert

  • response_format ('markdown' | 'json'): Output format

Returns: Converted amount with exchange rate.

Examples:

  • "Convert 1000 USD to EUR" -> from: "USD", to: "EUR", amount: 1000

  • "How much is 1 oz gold in USD?" -> from: "XAU", to: "USD", amount: 1

  • "Convert 0.5 BTC to USD" -> from: "BTC", to: "USD", amount: 0.5

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYesTarget currency code (e.g., EUR, JPY, USD)
fromYesSource currency code (e.g., USD, EUR, XAU)
amountYesAmount to convert
response_formatNoOutput format: 'markdown' for human-readable or 'json' for structured datamarkdown
Behavior4/5

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

Annotations already indicate read-only, idempotent behavior. The description adds context about real-time rates and supported asset types (fiat, metals, crypto), which is useful beyond 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?

The description is concise, well-structured with sections, and includes examples that are immediately helpful. Every sentence adds value.

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?

The description explains the return (converted amount with exchange rate) and provides examples, but lacks explicit structure of the output. Still sufficient for the tool's purpose.

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

Parameters4/5

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

Schema coverage is 100%, but the description adds examples and clarifies valid inputs (e.g., XAU, BTC), enhancing understanding beyond the schema alone.

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 clearly states the tool converts an amount between currencies using real-time rates, and it distinguishes itself from siblings like get_exchange_rate by including an amount parameter.

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 usage for currency conversion but does not explicitly mention when to use it versus alternatives like get_exchange_rate, or any exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sherajdev/twelvedata-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server