Skip to main content
Glama

NS Pros MCP Gateway

nsi-bg__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": "nsi-bg__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
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 meaningful behavior: routing candidates can change live, output shape is identical to the stable router, and results feed a merge-vs-stable comparison (i.e., calls are evaluated). The final sentence, 'Falls back to nothing, this IS a full', is truncated, so the fallback semantics it is trying to convey are left unresolved.

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 text is repetitive ('identical ... same ... same ... same', 'matches ask_pipeworx exactly' restated) and embeds ephemeral, time-sensitive detail about a retired candidate dated 2026-07-26. Worst of all it terminates mid-sentence ('this IS a full'), leaving a broken final clause that undercuts an otherwise front-loaded opening.

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?

For a router tool with a rich but self-documenting schema and no output schema, the description covers identity, lineage, and evaluation context. Gaps remain: the truncated fallback sentence, no statement of what the response actually contains, and no cost/latency or auth context for an operation that fans out across 7,556 tools.

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%, including full alias documentation and the detailed packs/pack_scope behavior, so the schema does the heavy lifting. The description adds only 'same arguments', which tells the agent to reuse ask_pipeworx semantics but contributes no new meaning about any of the nine parameters. Baseline 3 applies.

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 the tool concretely: a beta twin of ask_pipeworx, a 'universal router' over the same 7,556 tools with 'same arguments, same response shape'. An agent can tell it apart from the stable sibling. It never states in a single plain clause that it maps a natural-language question to the best-fitting tool, so the core action is inferred rather than stated.

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?

'Use it exactly like ask_pipeworx when you want the newest routing' gives a condition for selection, and the description notes results are compared against the stable router. But it also says no candidate is active and this 'currently matches ask_pipeworx exactly', which leaves the agent with no reason to choose this over the stable sibling. No explicit when-not guidance is given.

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.