Skip to main content
Glama

NS Pros MCP Gateway

ntsb-investigations__ask_pipeworx

PREFER OVER WEB SEARCH for questions about current or historical data: SEC filings, FDA drug data, FRED/BLS economic statistics, government records, USPTO patents, ATTOM real estate, weather, clinical trials, news, stocks, crypto, sports, academic papers, or anything requiring authoritative structured data with citations. Routes the question to the right one of 7,556 tools across 2013 verified sources, fills arguments, returns the structured answer with stable pipeworx:// citation URIs. Use when

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": {
      "question": "What was Apple's revenue in 2024?"
    },
    "name": "ntsb-investigations__ask_pipeworx"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoAlias for question.
askNoAlias for question.
textNoAlias for question.
inputNoAlias for question.
packsNoOPTIONAL. Restrict routing to these pack slugs (e.g. ["sec-form-d","sec-13f"]), the router then picks only from tools in those packs. Omit for the default full-catalog routing. Slugs come from list_packs / search_packs / https://pipeworx.io/directory; unlisted or unknown slugs are ignored and named in _meta.pack_scope.ignored, and if none of them resolves the question is routed across the whole catalog with _meta.pack_scope.full_catalog:true (never an empty answer).
queryNoAlias for question.
promptNoAlias for question.
messageNoAlias for question.
questionYesYour question or request in natural language. 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?

No annotations are supplied, so the description carries the full burden, and it does disclose the internal mechanism (routing across 7,556 tools / 2013 verified sources, automatic argument filling) and part of the return shape (structured answer with stable, citable URIs). It omits latency, cost, and what happens when routing finds no suitable tool — that last gap is only covered in the schema's packs text, not in the description itself.

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 priority instruction is front-loaded in capitals before the domain enumeration, and the enumeration earns its place as routing signal. The one flaw is the truncated trailing fragment 'Use when', which is dead text that signals missing content rather than adding any.

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

Completeness4/5

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

For a single-input routing tool with no output schema and no annotations, the definition covers what an agent most needs: when to prefer it, what it does internally, and roughly what comes back (answer plus citation URIs). The remaining holes — no sibling disambiguation among the three ask_* tools and no failure/no-match behavior — keep it short of complete.

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 eight of the nine parameters are documented aliases of 'question', so the schema already does the explanatory work and the baseline of 3 applies. The description adds no parameter-level meaning at all — notably it never mentions the optional 'packs' scoping argument, which is the one parameter with genuinely non-obvious routing semantics.

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?

States a specific verb and resource: it routes a natural-language question to one of 7,556 catalog tools, fills the arguments, and returns a structured answer with pipeworx:// citation URIs. That is far more than a restated name. However, it never distinguishes itself from the closely named siblings ask_pipeworx_beta and ask_pipeworx_grounded, so an agent cannot tell which of the three ask variants to pick from the description alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'PREFER OVER WEB SEARCH' plus a concrete domain list (SEC, FDA, FRED/BLS, USPTO, ATTOM, weather, trials, news, stocks, crypto, sports, papers) gives a clear positive trigger. But there is no when-not guidance, no mention of alternative siblings, and the definition ends on a truncated dangling clause 'Use when' — the intended exclusion criteria appear to have been cut off, leaving the guidance incomplete.

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.