Skip to main content
Glama

Tarot Draw

by io.github.pipeworx-io

Deep Research

deep_research
Read-onlyIdempotent

ACCOUNT REQUIRED (free — sign in via GitHub at https://pipeworx.io/signup; depth:"thorough" needs a paid plan). If you are not signed in, use ask_pipeworx instead — it works on every tier. Grounded multi-source research across Pipeworx's 1517 STRUCTURED data sources (SEC filings, FRED/BLS economics, FDA, USPTO patents, markets, science, government records, etc.) in ONE call — this is NOT open-web search. Decomposes your question into focused facets, routes each to the right one of 5,798 tools IN PARALLEL, and returns a findings packet: verbatim evidence + confidence + source + fetched_at + a stable pipeworx:// citation per finding, with explicit gaps[] for facets the data couldn't answer (never invented). Best for broad/multi-part questions over structured data ("compare X and Y's regulatory + financial exposure", "research the filings + market picture for ACME"). For a single lookup use ask_pipeworx (one LLM call, not many). For BREAKING or colloquial CURRENT-NEWS / "what's the world saying about X" topics, prefer ask_pipeworx — it routes to live news APIs and the *-news-feeds packs; deep_research returns mostly empty gaps[] when the topic isn't in the structured catalog. Second-hop iteration: depth:"standard" re-angles unanswered gaps (gap recovery); depth:"thorough" additionally chases the best leads from the first pass — so multi-step questions resolve in one call. Every finding carries a hop field and a citation_uri — a resolvable pipeworx:// record URI, present only when the source emits one that resources/read can actually serve, so a citation you get back is always fetchable. "standard" and "thorough" also return contradictions[] flagging findings that disagree. Large records are semantically excerpted to the passages relevant to each facet (not head-truncated), so answers deep in a long filing/series aren't missed. Expect 15-60s (thorough with its follow-up + contradiction pass: up to ~90s).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
depthNoHow many facets to research in parallel: quick=3 (single hop), standard=3 (default; adds a gap-recovery hop that re-angles unanswered facets + a contradictions[] scan across findings), thorough=6 (paid; adds a full iterative hop that chases leads + recovers gaps, plus the contradictions[] scan).
questionYesThe research question, in natural language. Broad/multi-part is fine — decomposition is the point.

Schema Changelog

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

  1. Changed1 schema field changed
    • changedInput schema / properties / depth / description
      Previous value: -"How many facets to research in parallel: quick=3 (single hop), standard=5 (default; adds a gap-recovery hop that re-angles unanswered facets + a contradictions[] scan across findings), thorough=8 (paid; adds a full iterative hop that chases leads + recovers gaps, plus the contradictions[] scan)."New value: +"How many facets to research in parallel: quick=3 (single hop), standard=3 (default; adds a gap-recovery hop that re-angles unanswered facets + a contradictions[] scan across findings), thorough=6 (paid; adds a full iterative hop that chases leads + recovers gaps, plus the contradictions[] scan)."
  2. Changed1 schema field changed
    • changedInput schema / properties / depth / description
      Previous value: -"How many facets to research in parallel: quick=3 (single hop), standard=5 (default; adds a gap-recovery hop that re-angles unanswered facets), thorough=8 (paid; adds a full iterative hop that chases leads + recovers gaps, plus a contradictions[] scan across findings)."New value: +"How many facets to research in parallel: quick=3 (single hop), standard=5 (default; adds a gap-recovery hop that re-angles unanswered facets + a contradictions[] scan across findings), thorough=8 (paid; adds a full iterative hop that chases leads + recovers gaps, plus the contradictions[] scan)."
  3. Changed1 schema field changed
    • changedInput schema / properties / depth / description
      Previous value: -"How many facets to research in parallel: quick=3, standard=5 (default), thorough=8 (paid plans). \"thorough\" also runs a second ITERATIVE hop — a planner inspects the first-pass findings/gaps and chases the most valuable leads or recovers gaps, resolving multi-step questions in one call."New value: +"How many facets to research in parallel: quick=3 (single hop), standard=5 (default; adds a gap-recovery hop that re-angles unanswered facets), thorough=8 (paid; adds a full iterative hop that chases leads + recovers gaps, plus a contradictions[] scan across findings)."
  4. Changed1 schema field changed
    • changedInput schema / properties / depth / description
      Previous value: -"How many facets to research in parallel: quick=3, standard=5 (default), thorough=8 (paid plans)."New value: +"How many facets to research in parallel: quick=3, standard=5 (default), thorough=8 (paid plans). \"thorough\" also runs a second ITERATIVE hop — a planner inspects the first-pass findings/gaps and chases the most valuable leads or recovers gaps, resolving multi-step questions in one call."
  5. Added

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnly/openWorld/idempotent behavior, but the description adds substantial context beyond them: account and paid-plan requirements, parallel decomposition across 5,798 tools, output shape with gaps[] and contradictions[], citation_uri fetchability, semantic excerpting, and latency expectations. This fully discloses what the agent should expect.

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 long but every sentence carries distinct information: auth, alternatives, data scope, decomposition behavior, output packet, gap handling, contradictions, citation fetchability, excerpting, and latency. Critical constraints are front-loaded at the beginning, so an agent sees the most decision-relevant facts immediately.

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 no output schema, the description carries the burden of explaining return values and does so thoroughly: verbatim evidence, confidence, source, fetched_at, stable citations, gaps[], contradictions[], hop field, and citation_uri. It also covers authentication, pricing, latency, exclusions, and alternatives, making it complete for a complex tool.

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 description coverage is 100%, so the baseline is 3. The description goes further by clarifying that depth:'thorough' needs a paid plan, that standard/thorough add gap-recovery and contradictions[], and that the question can be broad/multi-part. This adds real semantic value beyond the schema.

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 names a specific verb and resource: grounded multi-source research across Pipeworx's 1517 structured data sources, including SEC, FRED, FDA, USPTO, and more. It clearly distinguishes itself from open-web search and from single-lookup siblings by naming what it is not and what it is best at.

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?

The description gives explicit when-to-use guidance: best for broad/multi-part questions over structured data, with concrete examples. It also names the alternative explicitly for two exclusion cases: use ask_pipeworx if not signed in, and use ask_pipeworx for a single lookup. The depth tiers are also tied to usage scenarios.

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

All Tarot Draw 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

Multiple tool families have unclear boundaries: ask_pipeworx and ask_pipeworx_beta are explicitly identical right now, suggest_questions and discover_tools are near-duplicates, and ai_visibility_check is a subset of scan_competitor_ai_presence. The five polymarket_* tools are heavily overlapping in purpose and rely on long descriptions to distinguish them, which an agent must read carefully to avoid misselection.

Naming Consistency3/5

All names are lowercase snake_case and there are helpful prefixes (polymarket_*, ask_pipeworx_*, pipeworx_*), but the verb/noun ordering is inconsistent: verb-first names (generate_llms_txt, resolve_entity, scan_dependency) sit alongside noun-first names (bet_research, entity_profile, recent_changes) and bare verbs (forget, recall, remember). Sub-families are internally consistent, but the set as a whole follows no single convention.

Tool Count2/5

32 tools is over the 'too many' threshold, and the scope is a grab-bag rather than a focused server: data research, prediction-market analysis, npm dependency checks, llms.txt generation, memory utilities, subscriptions, and exactly one tarot tool. The server is named 'Tarot Draw' yet 31 of 32 tools serve a completely different purpose, making the count wildly mismatched to the apparent identity.

Completeness2/5

For the inferred Pipeworx data/prediction-market domain the coverage is genuinely deep — ask/grounded/deep research, entity resolution, profiles, comparisons, validation, subscriptions, alerts, edge tracking, and arbitrage all exist. But for the stated purpose ('Tarot Draw'), the surface is one draw tool with no deck details, spreads, reading history, or reversal support, and the data tools' domain is so diffuse that an agent cannot rely on the set forming a coherent workflow.

Resources