Skip to main content
Glama

Tcgdex

by io.github.pipeworx-io

Entity Profile

entity_profile
Read-onlyIdempotent

"Tell me about X" / "research Acme" / "brief me on Tesla" / "what does Apple do" / "company profile for Microsoft" / "give me the rundown on NVDA" / "everything you know about $TICKER" — full cross-source profile of a US public company in ONE parallel call. ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view. Fans out across SEC EDGAR, XBRL, USPTO patents, federal contracts (USAspending), FDA-licensed biologics (Purple Book), H-1B hiring (DOL LCA), news and GLEIF, and returns: cik + company_name (+ resolved_from/resolved_to when value was a name); recent_filings (up to 5 with pipeworx://edgar/company/{cik}/filings/{accession} URIs); fundamentals (LATEST 10-K Revenues + NetIncomeLoss + Cash, sorted period_end DESC); patents (USPTO PatentsView API sunset May 2025 — soft-fails until reactivated); federal_contracts (USAspending awards where the company is the recipient); fda_products (FDA-licensed biologics — vaccines, cell/gene therapies — from the Purple Book; a company with only small-molecule/generic drugs will show none here, that is expected, not a failure); hiring (H-1B sponsorship volume + salary range from DOL LCA filings); recent news mentions via GDELT→GNews fallback; LEI via GLEIF. sources_used / sources_failed say which of these actually returned data for THIS company — an empty section is a real "no data", not a bug. Pass a ticker ("AAPL"), zero-padded CIK ("0000320193"), OR a company name ("Moderna") — names now resolve via SEC EDGAR's company-name match; a private company (no CIK/ticker) returns resolved:false with an explicit notes line, not a bare failure. type accepts "company" or "ticker" interchangeably — both take the same value shapes above.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYes"company" or "ticker" — both are accepted and behave identically; `value` can be a ticker, CIK, or company name either way. person/place coming soon.
valueYesTicker (e.g., "AAPL"), zero-padded CIK (e.g., "0000320193"), or company name (e.g., "Moderna") — names resolve via SEC EDGAR company-name match.

TDQS

A4.6/5.0
Behavior5/5

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

The description adds context beyond annotations: fans out across multiple sources, returns specific fields, mentions USPTO sunset with soft-fail, and news fallback. Annotations already indicate read-only, idempotent, non-destructive; description reinforces and details the behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description is a single dense paragraph. While all content is valuable, it could benefit from bullet points or more structured formatting for easier scanning. Not overly verbose but not highly structured.

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?

Given no output schema, the description explains all return fields (cik, company_name, filings with URIs, fundamentals, patents with caveat, news, LEI). It is sufficiently complete for a broad-profile tool, though error handling or performance is not mentioned.

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%. Description adds meaning: type only 'company' for now, value must be ticker or zero-padded CIK, names not supported. This supplements the schema 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 function: 'full cross-source profile of a US public company in ONE parallel call.' It lists example queries and specific data sources (SEC, XBRL, USPTO, news, GLEIF) and distinguishes from siblings like resolve_entity and compare_entities.

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?

Explicitly advises to prefer this tool over chaining single-source lookups for holistic views. States constraints: only supports ticker or CIK, names not supported (use resolve_entity first). Provides clear when-to-use 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