Skip to main content
Glama

deckofcards

by io.github.pipeworx-io

Discover Tools

discover_tools
Read-onlyIdempotent

Find tools by describing the data or task. Use when you need to browse, search, look up, or discover what tools exist for: SEC filings, financials, revenue, profit, FDA drugs, adverse events, FRED economic data, Census demographics, BLS jobs/unemployment/inflation, ATTOM real estate, ClinicalTrials, USPTO patents, weather, news, crypto, stocks. Returns the top-N most relevant tools with names, descriptions, and full input schemas (with curated examples) — each result is ready to call directly, no second schema lookup needed. Call this FIRST when you have many tools available and want to see the option set (not just one answer).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoAlias for query.
taskNoAlias for query.
limitNoMaximum number of tools to return (default 20, max 50)
queryYesNatural language description of what you want to do (e.g., "analyze housing market trends", "look up FDA drug approvals", "find trade data between countries"). Accepts task, q, description, search as aliases.
searchNoAlias for query.
descriptionNoAlias for query.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed5 schema fields changed
    • addedInput schema / properties / description
      Added value: +{
+  "description": "Alias for query.",
+  "type": "string"
+}
    • addedInput schema / properties / q
      Added value: +{
+  "description": "Alias for query.",
+  "type": "string"
+}
    • changedInput schema / properties / query / description
      Previous value: -"Natural language description of what you want to do (e.g., \"analyze housing market trends\", \"look up FDA drug approvals\", \"find trade data between countries\")"New value: +"Natural language description of what you want to do (e.g., \"analyze housing market trends\", \"look up FDA drug approvals\", \"find trade data between countries\"). Accepts task, q, description, search as aliases."
    • addedInput schema / properties / search
      Added value: +{
+  "description": "Alias for query.",
+  "type": "string"
+}
    • addedInput schema / properties / task
      Added value: +{
+  "description": "Alias for query.",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "look up FDA drug approvals"
+  },
+  {
+    "query": "analyze housing market trends"
+  }
+]
  3. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already indicate readOnly, idempotent, and non-destructive behavior. The description adds valuable context beyond that: it returns the 'top-N most relevant tools with names, descriptions, and full input schemas (with curated examples)' and that each result is 'ready to call directly, no second schema lookup needed.' This discloses the tool's output behavior and efficiency, which is helpful and not redundant 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 organized into three clear sentences, with the main action and use case front-loaded. The long list of domains (SEC filings, FDA drugs, etc.) is a bit verbose but serves a purpose by signaling coverage and helping the agent match queries. It is efficient overall with no filler or repetition.

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?

There is no output schema, so the description compensates by explicitly stating the return value: 'top-N most relevant tools with names, descriptions, and full input schemas (with curated examples).' It also gives concrete usage timing ('Call this FIRST') and covers the tool's role, making the description complete for a read-only discovery tool with strong schema coverage.

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?

Input schema coverage is 100% and explicitly documents 'query' with aliases and 'limit' with default/max. The description mentions 'describing the data or task' (matching query) and 'top-N' (matching limit), but it adds no new semantic detail beyond what the schema already provides. Baseline 3 is appropriate because the schema carries the burden and the description does not contradict or extend it.

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 purpose: 'Find tools by describing the data or task.' It uses a specific verb-resource pair and differentiates itself from sibling tools by explicitly listing the domains it covers (SEC filings, FDA drugs, etc.) and by positioning itself as a discovery/catalog tool rather than a direct data-retrieval tool. The mention of returning 'top-N most relevant tools' further clarifies its role.

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 gives clear usage context: 'Use when you need to browse, search, look up, or discover what tools exist' and 'Call this FIRST when you have many tools available and want to see the option set.' This strongly implies when to use it, but it does not explicitly name alternatives or state when not to use it, so it falls just short of a 5.

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

All deckofcards 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

B3.4/5.0
Disambiguation2/5

Multiple tools have overlapping purposes: ask_pipeworx and ask_pipeworx_beta are functionally identical (beta just has experimental routing), and the Polymarket suite (bet_research, polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread) all revolve around prediction-market signal detection with unclear boundaries. Also ai_visibility_check and scan_competitor_ai_presence overlap heavily.

Naming Consistency2/5

Naming is a mix of verb-first (draw_cards, resolve_entity, discover_tools) and noun-first (entity_profile, new_deck, recent_alerts) styles, with inconsistent prefixes (pipeworx_feedback vs ask_pipeworx) and no unifying convention. Some tools are bare verbs (recall, remember), others are noun phrases (polymarket_edges).

Tool Count2/5

34 tools is excessive for a server named 'deckofcards' — only 3 tools relate to cards. Even as a general-purpose data/research server, 34 is on the high end and includes many near-duplicates (ask_pipeworx variants) and highly specialized tools that could be consolidated.

Completeness3/5

The research side is fairly complete (lookup, grounding, comparison, profiles, claim verification, memory, subscriptions), but the card-deck functionality is minimal (only create, draw, shuffle) and lacks any deck inspection or hand management. The server's scope is unclear, making it hard to assess true coverage.

Resources