Skip to main content
Glama

Twelvedata

by io.github.pipeworx-io

Subscribe to Alerts

subscribe
Idempotent

Create a proactive monitoring subscription to a live-data event stream. Returns the new subscription id. Requires a Pipeworx OAuth account (anonymous + BYO cannot persist subscriptions). Supported types: "sec_8k" (8-K filings matching ticker + item codes — e.g. items:["5.02"] = officer change), "polymarket_edge" (Polymarket↔Kalshi cross-venue mispricings — params:{topic:"fed"}), "fred_series" (new FRED observations — params:{series_id:"UNRATE"}). Delivery channels: feed (always on — pull via recent_alerts or GET registry.pipeworx.io/alerts.json), and optionally email (set delivery:{email:"you@x.com"}) or sms (delivery:{sms:"+15551234567"} — phone must be verified at /account first; 10/day cap).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesSubscription type.
paramsYesType-specific filter. sec_8k: {ticker:"AAPL", items?:["5.02","1.01"]}. polymarket_edge: {topic:"fed", min_spread_bps?:500}. fred_series: {series_id:"UNRATE"}. patent_grant: {applicant:"Apple Inc."}. clinical_trial: {sponsor?:"Pfizer", condition?:"lung cancer", phase?:"PHASE3"} (sponsor or condition required).
deliveryNoOptional delivery channels in addition to the always-on persistent feed. {email:"you@x.com"} sends a templated alert per fired event. {sms:"+15551234567"} sends an SMS per event — must match the verified phone on the caller's account (verify at https://pipeworx.io/account first; 10/day cap). {webhook:"https://..."} POSTs each event JSON to your endpoint, HMAC-signed — the response includes delivery.webhook_secret (whsec_…) ONCE; verify X-Pipeworx-Signature = sha256 HMAC of "<X-Pipeworx-Timestamp>.<raw body>". Auto-disabled after 10 consecutive failing runs.

TDQS

A4/5.0
Behavior2/5

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

The description says 'Returns the new subscription id,' implying each call creates a new subscription, which contradicts the idempotentHint annotation (idempotentHint=true). This is a significant inconsistency. On the positive side, it discloses OAuth requirements, delivery caps, and phone verification.

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 appropriately detailed for a complex subscription tool, with clear structure: purpose, authentication, types, delivery. Every sentence provides necessary information without redundancy.

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?

Despite lacking an output schema, the description covers return value (subscription ID), authentication, type-specific parameters, and delivery constraints. It does not detail error handling or idempotency, but is otherwise complete for a tool of this complexity.

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 substantial value by explaining enumeration options (e.g., sec_8k, polymarket_edge) with examples, detailing type-specific params, and clarifying delivery options including webhook signing. This goes beyond the schema's minimal descriptions.

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 creates a proactive monitoring subscription to a live-data event stream and returns a new subscription ID. This distinguishes it from sibling tools like list_subscriptions (list) and unsubscribe (remove).

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?

The description specifies that a Pipeworx OAuth account is required, excluding anonymous/BYO users, and notes the SMS 10/day cap and phone verification. However, it does not explicitly mention when to use this tool versus alternatives, though the context makes it clear.

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