Hk Stocks

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 1711 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 6,555 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

Name	Required	Description
`q`	No	Alias for question.
`ask`	No	Alias for question.
`text`	No	Alias for question.
`depth`	No	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).
`input`	No	Alias for question.
`query`	No	Alias for question.
`prompt`	No	Alias for question.
`message`	No	Alias for question.
`question`	Yes	The research question, in natural language. Broad/multi-part is fine — decomposition is the point. Accepts query, q, prompt, text, input, ask, message as aliases.

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedSep 24, 2026

addedInput schema / properties / ask

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

addedInput schema / properties / input

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

addedInput schema / properties / message

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

addedInput schema / properties / prompt

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

addedInput schema / properties / q

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

addedInput schema / properties / query

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

changedInput schema / properties / question / description

Previous value: -"The research question, in natural language. Broad/multi-part is fine — decomposition is the point."New value: +"The research question, in natural language. Broad/multi-part is fine — decomposition is the point. Accepts query, q, prompt, text, input, ask, message as aliases."

addedInput schema / properties / text

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

Changed1 schema field changedSep 19, 2026

addedInput schema / examples

Added value: +[
+  {
+    "depth": "quick",
+    "question": "What is the current US unemployment rate and how has it changed over the past year?"
+  }
+]

First observedSep 15, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only cover the safety profile (readOnly/openWorld/idempotent/non-destructive). The description adds auth requirements (account, paid plan for thorough), latency expectations (15-60s, up to ~90s), return anatomy (findings packet, gaps[], contradictions[], hop, citation_uri), and a semantic-excerpting behavior — none derivable from 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?

Front-loaded with the account requirement and information-dense throughout. It is on the long side with some repetition (ask_pipeworx referenced for several distinct cases), but each clause carries actionable detail for a genuinely complex tool.

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?

No output schema exists, so the description carries the return-value burden and does so fully: it explains the findings packet contents, gaps[], contradictions[], hop field, and that citation_uri is always fetchable. Auth, latency, and failure modes are all covered.

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 depth enum is already documented. The description still adds value by framing depth as second-hop iteration semantics (gap recovery vs. lead-chasing) and by noting depth:'thorough' requires a paid plan, which is not 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?

States a specific verb+resource (grounded multi-source research) with explicit scope: 1711 STRUCTURED data sources, in ONE call, 'this is NOT open-web search.' It distinguishes itself from ask_pipeworx (single lookup / news) and from generic web search, so an agent can disambiguate without opening schemas.

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?

Gives explicit when-to-use and when-not-to-use: not signed in → ask_pipeworx; single lookup → ask_pipeworx; breaking/colloquial current-news → ask_pipeworx because deep_research returns empty gaps[]. It names the alternative and the selecting condition for each case.

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

All Hk Stocks tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Deep Research

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources