Skip to main content
Glama

NS Pros MCP Gateway

numverify__deep_research

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 2013 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 7,556 tools IN PA

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "depth": "quick",
      "question": "What is the current US unemployment rate and how has it changed over the past year?"
    },
    "name": "numverify__deep_research"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoAlias for question.
askNoAlias for question.
textNoAlias for question.
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).
inputNoAlias for question.
queryNoAlias for question.
promptNoAlias for question.
messageNoAlias for question.
questionYesThe 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.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose non-obvious behavior: auth is required, 'thorough' costs a paid plan, work is fanned out into facets routed across 7,556 tools in one call, and it hits structured rather than web data. It does not disclose latency, cost/rate limits, or what the response looks like. The final sentence is also truncated mid-word ('IN PA'), leaving the routing explanation incomplete.

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 critical constraint (account required) is correctly front-loaded and the exclusion of web search is prominent. However, the text terminates mid-sentence, so the routing explanation ends abruptly and the definition reads as truncated rather than deliberate.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Auth, tier gating, and routing behavior are covered, but there is no output schema and the description never describes what a caller receives (findings, sources, contradictions[]). For a multi-hop research tool pulling from thousands of sources, that missing return-value picture is a meaningful gap.

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 baseline is 3; the description adds real meaning by tying depth:'thorough' to a paid-plan prerequisite, which is not visible in the schema. The alias cluster (query/q/prompt/text/input/ask/message) and facet decomposition are already documented in the schema, so no extra credit there.

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 across ... 2013 STRUCTURED data sources') and explicitly excludes a neighboring interpretation ('this is NOT open-web search'), listing concrete source domains. It also names the sibling alternative (ask_pipeworx) so an agent can distinguish this tool from a lighter one.

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?

Gives explicit context: sign-in requirement, the paid-tier condition for depth:'thorough', and a clear fallback rule ('If you are not signed in, use ask_pipeworx instead'). The gap is that the sibling list contains many domain-scoped *_deep_research tools, and the description never explains when to pick this cross-domain version over a domain-specific one.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.