Skip to main content
Glama

Twelvedata

by io.github.pipeworx-io

Exchange Rate

exchange_rate
Read-onlyIdempotent

Twelve Data live forex exchange rate for a currency pair symbol (e.g. 'EUR/USD'). Optional dp (decimal places) and timezone. Returns rate, timestamp, and pair identifiers.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dpNoDecimal places for the rate (0–11).
formatNoResponse format: "JSON" (default) or "CSV".
symbolYesTicker/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").
timezoneNoOptional timezone, e.g. "America/New_York" or "UTC".

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeNoResponse code
statusNoResponse status
messageNoResponse message

TDQS

B3.4/5.0
Behavior3/5

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

Annotations (readOnlyHint, idempotentHint, destructiveHint) already convey safety and idempotency. The description adds that the tool returns 'rate, timestamp, and pair identifiers', but does not fully align with the schema's broader asset scope, reducing transparency.

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?

Single sentence, front-loaded with essential information. Every word earns its place without redundancy.

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

Completeness2/5

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

Despite having an output schema and annotations, the description incorrectly restricts the tool to 'forex' while the schema supports stocks, crypto, indices, and ETFs. This incomplete and contradictory context undermines completeness for an agent.

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 coverage is 100% with detailed parameter descriptions (e.g., symbol supports multiple asset types and batch queries). The description only mentions symbol, dp, and timezone briefly, adding no significant meaning beyond the 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 clearly states the tool provides live forex exchange rate for a currency pair symbol, e.g., 'EUR/USD'. It uses a specific verb ('returns') and resource ('exchange rate'). While sibling tools like 'currency_conversion' and 'forex_pairs' exist, the focus on live forex rate distinguishes it, though not explicitly.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. The description says 'live forex exchange rate' but the 'symbol' parameter includes stocks, crypto, etc., creating a mismatch that could mislead agents about appropriate use cases.

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

All Twelvedata toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation3/5

While many tools have distinct purposes, there is notable overlap between price, quote, eod, and time_series for price data. Also, the multiple ask_pipeworx variants and deep_research could cause confusion about which to use for factual queries. Some tools like bet_research and polymarket_arbitrage also have overlapping domains.

Naming Consistency4/5

Most tools follow a descriptive snake_case pattern (ai_visibility_check, ask_pipeworx, compare_entities). A few are single words (cryptocurrencies, indices, profile) which is acceptable. No mixing of camelCase or other conventions, so consistent overall.

Tool Count2/5

47 tools is quite high for a single server. While the domain is broad (financial data, prediction markets, SEC filings, etc.), many tools are highly specific (e.g., polymarket_arbitrage, bet_research, scan_dependency) and could be consolidated. The count feels bloated and adds cognitive load.

Completeness4/5

The tool set is impressively comprehensive, covering stocks, forex, crypto, economic data, SEC filings, prediction markets, entity resolution, and even claims validation. Minor gaps exist (e.g., limited drug data despite having some tools), but overall the surface supports a wide range of agentic workflows without obvious missing operations.

Resources