Skip to main content
Glama

Twelvedata

by io.github.pipeworx-io

Indices

indices
Read-onlyIdempotent

Twelve Data reference list of all supported market index symbols (e.g. SPX, DJI) with exchange metadata. Use to discover or validate index tickers before querying time_series.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolNoOptional index filter (e.g. "IXIC").
countryNoOptional country filter (e.g. "United States").

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeNoResponse code
statusNoResponse status
messageNoResponse message

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare idempotent, read-only, non-destructive, and open-world behaviors. The description adds that it's a reference list with exchange metadata, which is useful but not critical beyond annotations. No contradictions.

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 concise sentences: first defines the tool's output, second states its recommended use. No superfluous information, perfectly front-loaded.

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 reference tool with full schema coverage, output schema, and robust annotations, the description adequately covers purpose and usage. No further details needed.

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?

Input schema coverage is 100%, so baseline is 3. The description does not add additional meaning about parameter usage beyond what the schema already provides (e.g., optional filters). The examples in schema suffice.

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 is a reference list of market index symbols with exchange metadata, giving concrete examples (SPX, DJI). It distinguishes itself from siblings like time_series by specifying its use for discovery/validation before querying that sibling.

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

Usage Guidelines5/5

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

Explicitly advises to use this tool to discover or validate index tickers before querying time_series, providing clear contextual guidance. It implies not to use it for direct data retrieval, aligning with its reference nature.

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