Skip to main content
Glama

NS Pros MCP Gateway

ntsb-investigations__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": "ntsb-investigations__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

A3.7/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does substantial work: it discloses the authentication prerequisite, the paid-tier gate on the 'thorough' depth, the scope of the underlying corpus (2013 structured sources), and the key behavioral contrast that this is not web search. It stops short of stating latency, cost per call, or what a result set looks like, which matters for a fan-out research tool.

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 gating information is correctly front-loaded, but the body is one overstuffed sentence that crams corpus description, decomposition mechanics, and tool-routing together, and it terminates mid-clause. The parenthetical signup URL and pricing note are useful; the run-on construction is not.

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?

Nine parameters, no annotations, and no output schema mean the description must stand in for the return contract, and it does not — there is no statement of whether results are findings with citations, source URLs, or structured facets, only a passing mention of a contradictions[] scan in the schema. Combined with the truncated final sentence, an agent can decide whether to call this but not what it will get back.

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 coverage is 100%, and the schema already spells out the depth enum in detail (facet counts, gap-recovery hop, contradictions scan) plus the full alias list. The description adds only one thing beyond that: the paid-plan constraint on depth 'thorough'. That is real value, but the schema is doing nearly all the parameter work, so the baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 over structured data sources (SEC, FRED/BLS, FDA, USPTO, etc.) in one call, and explicitly negates the nearest misreading with 'this is NOT open-web search.' It also routes the unsigned-in agent to ask_pipeworx. The only deduction is that the sentence describing decomposition and routing is cut off mid-word ('7,556 tools IN PA'), leaving the mechanism incompletely stated.

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 gating conditions rather than vague context: an account is required, depth 'thorough' requires a paid plan, and agents that are not signed in should use ask_pipeworx instead. What it does not cover is how this compares to the other research-flavored siblings present in the catalog (bet_research, research_row, ask_pipeworx_grounded), so the agent must infer those boundaries.

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.