Skip to main content
Glama

NS Pros MCP Gateway

ntsb-investigations__ask_pipeworx_beta

Beta version of ask_pipeworx: identical universal router (same 7,556 tools, same arguments, same response shape) with candidate routing improvements enabled live whenever one is under test. No candidate is active right now (the last was retired on outcome evidence 2026-07-26), so this currently matches ask_pipeworx exactly. Use it exactly like ask_pipeworx when you want the newest routing; results are compared against the stable router to decide what merges. Falls back to nothing, this IS a full

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 is the current US unemployment rate?"
    },
    "name": "ntsb-investigations__ask_pipeworx_beta"
  }
}

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

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose useful context beyond a bare description: the experimental nature, the evidence-based retirement of the last candidate, and that results are compared against the stable router. However, it says nothing about latency, failure behavior, or what a response actually contains beyond "same response shape," and the trailing sentence is cut off mid-thought.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening sentence is front-loaded and useful, but the body drifts into internal process detail (retirement date, merge comparison) and the final clause is an unfinished fragment ("this IS a full"), which is a real defect rather than mere brevity. A reader has to parse three separate statements of "it currently matches ask_pipeworx" to extract the actionable fact.

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?

The tool has 9 fully documented parameters and no output schema, so the description should at least convey the shape of the result; "same response shape" defers to an unstated sibling rather than explaining the return. Combined with the truncated closing sentence, enough is present to invoke it correctly but not to predict the response.

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% across all 9 parameters, with every alias for "question" and the full packs routing/fallback semantics documented inline. The description only repeats "same arguments" and adds no routing nuance beyond what the schema already provides, 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 identifies this as a beta mirror of ask_pipeworx: a universal natural-language router over the same 7,556 tools, arguments and response shape, with candidate routing experiments live. That is a specific resource and it explicitly differentiates itself from the stable sibling ask_pipeworx. The truncated final clause ("Falls back to nothing, this IS a full") blunts the otherwise clear purpose statement.

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 says to use it exactly like ask_pipeworx "when you want the newest routing," which names the alternative and the condition that selects it. It also discloses that no candidate is currently active so it behaves identically to the stable router. It stops short of an explicit recommendation to prefer ask_pipeworx while no experiment is live, which an agent would want stated outright.

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.