Skip to main content
Glama

NS Pros MCP Gateway

nvd__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": "nvd__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

A3.5/5.0
Behavior3/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 useful traits: identical argument surface, identical response shape, live candidate-routing behavior, and the comparison/merge workflow. However, the final sentence is truncated ('Falls back to nothing, this IS a full'), leaving the fallback semantics undefined, and it says nothing about latency, cost, side effects, or what happens when no tool matches.

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 beta/stable distinction is front-loaded, which is correct, but the prose is padded with parenthetical repetition ('same 7,556 tools, same arguments, same response shape') and ends in a dangling fragment that conveys nothing. Trimming the redundancy and completing or cutting the final clause would materially improve it.

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 taking one natural-language question plus optional pack scoping and returning no declared output schema, the description should characterize the response. It instead defers to 'same response shape' as ask_pipeworx, whose shape the agent cannot see here, and leaves the fallback sentence unfinished. Adequate for invocation, incomplete for interpreting results.

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%, so the aliases and the packs scoping parameter (including ignored-slug and full_catalog behavior) are already fully documented in the schema. The description adds only 'same arguments' as ask_pipeworx, which gives no extra meaning about individual 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 names the resource (a universal router over 7,556 tools) and qualifies it as the beta counterpart of ask_pipeworx with identical arguments and response shape. That makes it distinguishable from the stable router. It never states in one plain sentence that it routes a natural-language question to the best-fitting tool, so the core action is inferred from 'router' and 'routing' rather than declared.

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 an explicit selection rule: use it like ask_pipeworx 'when you want the newest routing,' and explains the results feed a comparison against the stable router. It also discloses that no candidate is currently active, which is effectively a when-not-signal (right now it is redundant with the stable tool). No explicit instruction on which to prefer when both are viable, so it stops short of a 5.

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.