Skip to main content
Glama

Twelvedata

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Forex Pairs

forex_pairs
Read-onlyIdempotent

Twelve Data reference list of all supported forex currency pairs (e.g. EUR/USD). Use to enumerate or validate pair symbols before querying exchange_rate or time_series.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolNoOptional pair filter (e.g. "EUR/USD").
currency_baseNoOptional base currency (e.g. "EUR").
currency_quoteNoOptional quote currency (e.g. "USD").

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeNoResponse code
statusNoResponse status
messageNoResponse message

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / currency_base
      Added value: +{
+  "description": "Optional base currency (e.g. \"EUR\").",
+  "type": "string"
+}
    • addedInput schema / properties / currency_quote
      Added value: +{
+  "description": "Optional quote currency (e.g. \"USD\").",
+  "type": "string"
+}
    • addedInput schema / properties / symbol
      Added value: +{
+  "description": "Optional pair filter (e.g. \"EUR/USD\").",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -true
  3. Changed2 schema fields changed
    • 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"
+}
  4. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive nature. Description adds value by specifying it's a 'reference list' from 'Twelve Data' and intended for enumeration/validation. No contradiction.

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. Key information is 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?

With an output schema present and only optional parameters, description sufficiently covers purpose, usage context, and sibling tool linkage. No gaps.

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 clear parameter descriptions. Description only reiterates the filter pattern without adding new meaning. 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?

Uses specific verbs 'enumerate or validate' on a clear resource 'forex currency pairs'. Distinguishes from siblings by naming 'exchange_rate' and 'time_series' as downstream tools.

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

Usage Guidelines4/5

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

States explicitly to use 'before querying exchange_rate or time_series', providing clear context. Does not include explicit exclusions but the usage scenario is well-defined.

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
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.

Resources