Skip to main content
Glama

microlink

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 1506 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,767 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.8/5.0
Behavior5/5

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

Beyond readOnly/openWorld/idempotent annotations, the description discloses account requirements, plan gating for 'thorough', latency (15-60s, up to ~90s), parallel decomposition behavior, gap reporting with 'never invented' guarantees, resolvable citations, semantic excerpting, hop fields, and contradiction scans. No statement contradicts the 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 carries operational or routing information: prerequisites, alternatives, output shape, provenance, failure behavior, and latency. It is front-loaded with the most critical constraint (account required) and the most common fallback (ask_pipeworx). Some length could be trimmed, but no sentence is filler.

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, the description fully explains what the tool returns: verbatim evidence, confidence, source, fetched_at, stable pipeworx:// citations, hop field, gaps[], and contradictions[] for standard/thorough. It also covers expected latency, auth prerequisites, and when not to use the tool, leaving no critical calling decision underspecified.

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?

The schema already documents both parameters at 100% coverage, but the description adds real value: it explains the depth tiers behaviorally ('standard' re-angles unanswered gaps, 'thorough' chases leads), notes that 'thorough' is paid, and clarifies that broad/multi-part questions are expected. This goes beyond the enum labels in 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 states a precise verb and resource: 'Grounded multi-source research across Pipeworx's 1506 STRUCTURED data sources' in ONE call, with 'NOT open-web search' explicitly delimiting scope. It differentiates from siblings by explaining decomposition into facets and parallel routing to 5,767 tools, and explicitly contrasts with ask_pipeworx for single lookups.

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?

Usage guidance is explicit and actionable: use deep_research for broad/multi-part questions over structured data, use ask_pipeworx for single lookups or when not signed in, and prefer ask_pipeworx for breaking/current-news topics. The description also gives tier-specific expectations and calls out when deep_research will mostly return gaps.

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

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

A4/5.0
Disambiguation4/5

Most tools have clearly distinct purposes with detailed usage guidance, but the several query entry points (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research) overlap conceptually and require careful reading to select correctly. Notably, ask_pipeworx_beta currently behaves identically to ask_pipeworx, which could cause confusion.

Naming Consistency3/5

Tool names mix verb-first (remember, resolve_entity) and noun-first (entity_profile, deep_research) patterns, with some using prefixes like 'polymarket_' or 'ask_pipeworx'. While all are snake_case and readable, the lack of a single consistent convention makes the set feel less coherent than it could be.

Tool Count3/5

33 tools is on the high end for a single server, though the broad domain (data retrieval, prediction markets, memory, subscriptions, web scraping) justifies much of the sprawl. Still, the count borders on heavy, and some tools could potentially be consolidated (e.g., the ask_pipeworx variants).

Completeness4/5

The toolset provides comprehensive coverage for its core data querying and analysis domain, with lifecycle coverage for memory and subscriptions. Minor gaps exist, such as no generic 'fetch page content' tool despite having get_metadata and take_screenshot, but these do not undermine the primary functionality.

Resources