Skip to main content
Glama

NS Pros MCP Gateway

nj-mvc__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": "nj-mvc__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.2/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does disclose genuinely load-bearing behavior: authentication is mandatory, the thorough depth is gated behind a paid plan, and the tool hits structured sources rather than the open web. It does not state latency, rate limits, or how many sources a single call will touch, which are material for a tool that fans out across thousands of tools.

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 auth requirement is front-loaded, which is the right priority for an agent deciding whether it can call this at all, and the tier/alternative guidance follows immediately. It is dense but each sentence carries routing or capability information; the only cost is that the final clause is cut off mid-sentence, leaving the tool-routing explanation incomplete.

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?

For a tool with no annotations and no output schema, the description supplies what an agent needs before calling: access gating, tier semantics, what data is covered, what is not covered, and the internal decomposition model. Return shape is not spelled out, but the depth parameter already references the findings and contradictions[] a call produces.

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?

Schema description coverage is 100%, and the schema already documents every alias and gives a detailed depth enum explanation (hop counts, gap recovery, contradictions[] scan). The description adds nothing about parameters beyond what the schema provides, so the baseline 3 applies.

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+resource ('Grounded multi-source research') and states the exact corpus it draws on (SEC filings, FRED/BLS, FDA, USPTO, markets, etc.) plus an explicit negative ('this is NOT open-web search'). It also describes the internal mechanism (decompose into facets, route to 7,556 tools), which is enough for an agent to distinguish it from generic search or ask_pipeworx without opening the schema.

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?

It gives explicit eligibility conditions ('ACCOUNT REQUIRED... depth:"thorough" needs a paid plan') and an explicit fallback ('If you are not signed in, use ask_pipeworx instead, it works on every tier'). What's missing is guidance on when to prefer this over the other research siblings (bet_research, research_row) once the agent IS signed in, leaving that choice to inference.

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.