Skip to main content
Glama

NS Pros MCP Gateway

nobel__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": "nobel__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.3/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. It does disclose useful behavior beyond structure: candidate routing is live only when under test, results are compared against the stable router, and the argument/response shape matches ask_pipeworx. But it omits error modes, response contents, and ends mid-sentence with 'Falls back to nothing, this IS a full,' so fallback behavior is never actually explained.

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 opening positions the tool well and the beta/stable relationship is front-loaded, but the final clause is a truncated fragment ('Falls back to nothing, this IS a full') that wastes space and signals an unfinished definition. Several sentences restate the equivalence to ask_pipeworx instead of adding information.

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 9-parameter router with no output schema, an agent still lacks a description of what comes back ('same response shape' points at another tool rather than explaining anything) and the fallback sentence is cut off. The parameter surface is covered by the schema, so the remaining gaps are moderate rather than fatal.

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 coverage is 100%, including a detailed description of the optional `packs` scoping parameter and its _meta.pack_scope fallback semantics, so the schema does the heavy lifting. The description adds only 'same arguments' and no meaning about the aliases or the `packs` behavior, which is the correct baseline-3 outcome when the schema is complete.

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 this is a 'universal router' over 'same 7,556 tools' with the same arguments and response shape as ask_pipeworx, which makes the resource and function identifiable. It is clear what it is, but it never plainly says in one phrase that it routes a natural-language question to the best-fitting tool, and it does not differentiate itself from the many sibling *__ask_pipeworx_beta entries.

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?

It gives one conditional instruction: 'Use it exactly like ask_pipeworx when you want the newest routing.' However, it immediately undercuts that by stating no candidate is active and it 'currently matches ask_pipeworx exactly,' leaving no real criterion for choosing this over the stable router and no when-not-to-use guidance.

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.