Skip to main content
Glama

Tcgdex

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

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

Discloses behavioral traits beyond annotations: requires OAuth, returns new ID, delivery limitations (SMS cap, webhook auto-disable after 10 failures). Annotations indicate idempotent and not destructive; description confirms creation and adds details. 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single paragraph packs all necessary info without wordiness. Logically orders: purpose, requirement, types, delivery. Could benefit from bullet points for readability, but no redundancy. Every sentence contributes.

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 complexity (multiple types, parameters, delivery modes, prerequisites), the description covers return value, authorization, type-specific configs, delivery options, and failure behaviors. Without output schema, it adequately describes the return (subscription id). No missing essential details.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but description adds substantial meaning: explains each type (e.g., sec_8k items codes, polymarket_edge topics), params object with examples, delivery object with constraints (phone verification, webhook signing). Goes far 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 action ('create a proactive monitoring subscription') and the resource ('live-data event stream'), with explicit return value ('Returns the new subscription id'). It distinguishes from siblings like list_subscriptions and unsubscribe by focusing on creation, and details types and delivery channels.

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?

Provides explicit prerequisites (Pipeworx OAuth account), lists supported types with parameters, and delivery channel constraints (phone verification, daily caps, webhook restrictions). Implicitly guides when to use recent_alerts instead for pulling. Lacks explicit when-not-to-use statements but offers clear context.

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

All Tcgdex 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
Disambiguation2/5

The four card tools are distinct, but the majority of the server is a Pipeworx/prediction-market platform with heavily overlapping entry points: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, and discover_tools all serve similar query/discovery purposes, and ask_pipeworx_beta is explicitly an identical twin of ask_pipeworx. The six Polymarket tools and the ai_visibility/scan_competitor pair also have fuzzy boundaries that would make tool selection error-prone.

Naming Consistency2/5

All names are snake_case, but the pattern is highly inconsistent: some are verb_noun (get_card, search_cards, resolve_entity), some are bare verbs (remember, forget), some are noun-first (polymarket_edges, entity_profile, bet_research), and some are adjective_noun (recent_alerts, recent_changes). The ask_pipeworx variants share a name but differ only by suffix, which is not a clear action-oriented pattern.

Tool Count2/5

35 tools is squarely in the 'too many' territory, and the bloat is worse because the server is named Tcgdex while only 4 of 35 tools actually relate to trading cards. The remaining 31 tools form a sprawling multi-domain platform that mixes data queries, prediction markets, memory, subscriptions, AI visibility checks, and one-off utilities like generate_llms_txt and scan_dependency.

Completeness4/5

For the TCGdex card surface, the read-only workflows are covered well: search_cards leads to get_card, and list_sets leads to get_set, with no obvious dead ends. For the broader Pipeworx functionality, the set includes discovery, query, grounding, entity resolution, memory, subscriptions, and feedback, so the main workflows are supported—though the overall scope is sprawling rather than focused.

Resources