Twelvedata

Stocks

stocks

Read-onlyIdempotent

Twelve Data reference list of all supported stock symbols with exchange and country metadata. Use to discover or validate tickers before querying price endpoints.

Input Schema

TableJSON Schema

Name	Required	Description
`type`	No	Optional instrument type filter (e.g. "Common Stock").
`symbol`	No	Optional ticker filter (e.g. "AAPL").
`country`	No	Optional country filter (e.g. "United States").
`exchange`	No	Optional exchange filter (e.g. "NASDAQ", "NYSE", "Binance").

Output Schema

TableJSON Schema

Name	Required	Description
`code`	No	Response code
`status`	No	Response status
`message`	No	Response message

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedJun 24, 2026

addedInput schema / properties / country

Added value: +{
+  "description": "Optional country filter (e.g. \"United States\").",
+  "type": "string"
+}

addedInput schema / properties / exchange

Added value: +{
+  "description": "Optional exchange filter (e.g. \"NASDAQ\", \"NYSE\", \"Binance\").",
+  "type": "string"
+}

addedInput schema / properties / symbol

Added value: +{
+  "description": "Optional ticker filter (e.g. \"AAPL\").",
+  "type": "string"
+}

addedInput schema / properties / type

Added value: +{
+  "description": "Optional instrument type filter (e.g. \"Common Stock\").",
+  "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: +[
+  {}
+]
```

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.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, covering safety and behavior. The description adds useful context about the data returned (exchange and country metadata), but does not disclose additional traits like pagination or rate limits, which is acceptable given the 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?

Two concise sentences with no wasted words. The first sentence defines the tool, the second provides usage guidance. Efficient and effective.

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?

Given the tool's simplicity (reference list with optional filters), the description is complete. Output schema exists, so return values need not be explained. No gaps for the intended use case.

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 input schema already documents all four optional parameters. The description does not add further meaning beyond the schema, which is expected when schema is complete. Baseline 3 is appropriate.

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 provides a reference list of supported stock symbols with metadata, and explicitly states its purpose: to discover or validate tickers before querying price endpoints. This distinguishes it from sibling tools like 'price' or 'quote' that handle price data.

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?

The description explicitly advises using this tool to discover or validate tickers before querying price endpoints, providing clear guidance on when to use it. This differentiates it from price-related siblings.

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.