Skip to main content
Glama

Tcgdex

by io.github.pipeworx-io

Send Pipeworx Feedback

pipeworx_feedback

Tell the Pipeworx team something is broken, missing, or needs to exist. Use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog (feature/data_gap), or when something worked surprisingly well (praise). ONLY for tools served by this Pipeworx connection — if the tool came from a different MCP server in your client (another vendor's Gmail, Splunk, Slack, etc. connector), we cannot fix it and reporting it here only delays you; file it with that server instead. Not sure? Pipeworx tool names are the ones this connection lists. Describe the issue in terms of Pipeworx tools/packs — don't paste the end-user's prompt. Filing without an account returns a claim_token; pass it back later as pipeworx_feedback({claim_token:"pwfb_…"}) to read whether it was fixed and what changed. The team reads digests daily and signal directly affects roadmap. Rate-limited to 5 per identifier per day. Free; doesn't count against your tool-call quota.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNobug = something broke or returned wrong data. feature = a new tool or capability you wish existed. data_gap = data Pipeworx does not currently expose. praise = positive note. other = anything else.
contextNoOptional structured context: which tool, pack, or vertical this relates to.
messageNoYour feedback in plain text. Be specific (which tool, what error, what data was missing). 1-2 sentences typical, 2000 chars max.
claim_tokenNoRead the reply to a report you filed earlier: pass the `pwfb_…` token that filing returned, with no other arguments. Returns the status and, once resolved, what actually changed.

TDQS

A4.8/5.0
Behavior5/5

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

Annotations provide minimal info (all false), so the description carries the transparency burden. It discloses rate limits (5 per identifier per day), that it is free and doesn't count against quota, the token issuance/redemption flow, and that the team reads digests daily. No contradictions with annotations.

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?

The description is long but every sentence earns its place, covering purpose, usage, exclusions, token flow, and limits. It is well-front-loaded with the core purpose. Some fringe details (roadmap impact) could be trimmed, but overall efficiently structured.

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 no output schema and all-false annotations, the description compensates fully: it explains the feedback flow, token retrieval, rate limits, quota, and scope restrictions. An agent has all necessary context to invoke the tool correctly in both filing and follow-up modes.

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%, so the baseline is 3. The description adds meaningful usage nuance: avoid pasting end-user prompts, the claim_token round-trip pattern, and how to describe issues in terms of Pipeworx tools/packs. This goes beyond the schema's parameter 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's function: telling the Pipeworx team something is broken, missing, or needs to exist. It explicitly lists feedback types (bug, feature/data_gap, praise) and is sharply distinguished from all sibling tools, being the only feedback mechanism in the catalog.

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?

Provides explicit when-to-use criteria: use for bugs (wrong/stale data), feature/data_gap requests, or praise. It also gives an exclusion rule (only for tools from this Pipeworx connection, not other MCP servers) and instructs how to follow up with a claim_token. This is model-tier guidance.

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