Skip to main content
Glama

NS Pros MCP Gateway

nplg-catalog__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": "nplg-catalog__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
Behavior4/5

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

With no annotations, the description does real work: it discloses that candidate routing is enabled live and can change answers between calls, that results are compared against the stable router, that unknown pack slugs are ignored and surfaced in _meta.pack_scope, and that there is no fallback. This is above-and-beyond behavioral context for a routing tool. It loses a point for the truncated final clause, which appears to be the actual statement about fallback behavior, and for saying nothing about latency, cost, or auth.

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 core routing facts are front-loaded in the first sentence, which is good structure. But the text is repetitive (restating 'same arguments, same response shape' and again 'matches ask_pipeworx exactly') and ends mid-clause with 'this IS a full', leaving a dangling, ungrammatical fragment that reads as an editing failure rather than concision.

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 with 9 parameters (mostly aliases) and no output schema, the description is reasonably complete about mechanics and scope. The gaps are real though: 'same response shape' offloads the return contract to a sibling the agent may not have loaded, and the tool's own fallback behavior is described only in a truncated fragment, leaving that contract ambiguous.

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 schema already documents the question field, all seven aliases, and the packs scoping semantics including _meta.pack_scope.ignored and full_catalog fallback. The description only adds 'same arguments' as ask_pipeworx and does not elaborate on any parameter beyond that. Baseline 3 is appropriate when the schema carries the parameter burden.

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 states a specific resource and mechanism: a 'universal router' over '7,556 tools' that takes a natural-language question. It explicitly differentiates itself from the stable sibling ('identical ... to ask_pipeworx', beta with candidate routing), so an agent can tell what it is and how it relates to the non-beta variant. The final sentence is truncated ('this IS a full'), which blunts the ending but does not obscure the core purpose.

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 when-to-use condition, and the note that no candidate is active right now is a useful signal. However, it never states when NOT to use it (e.g. prefer the stable router for production/repeatable answers) and never names ask_pipeworx_grounded as an alternative. The guidance is implied rather than stated as an explicit decision rule.

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.