Skip to main content
Glama

NS Pros MCP Gateway

numverify__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": "numverify__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 at all, the description carries the full behavioral burden; it does disclose useful non-obvious traits (live candidate routing, telemetry-style comparison against the stable router, identical response shape, and that unknown pack slugs are ignored rather than erroring — that last point lives in the schema). However, the final sentence is truncated ('Falls back to nothing, this IS a full'), leaving the fallback and completeness guarantees unresolved, and there is no mention of latency, cost, or error behavior for a beta endpoint.

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 message is front-loaded in the first two sentences, which is good, but the opening is padded with redundant restatements ('identical ... same arguments, same response shape ... matches ask_pipeworx exactly'), and the text cuts off mid-clause in the final sentence, leaving a dangling fragment that wastes space and creates ambiguity.

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?

There is no output schema, so the description must stand in for return-value expectations; it does so only by asserting 'same response shape' as ask_pipeworx, which assumes prior knowledge. For a 9-parameter (alias-heavy) router with zero annotation coverage, the definition covers routing/selection adequately but leaves the response contract and the truncated fallback statement unfinished.

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% and the alias parameters (`q`, `ask`, `text`, `input`, `query`, `prompt`, `message`) plus the `packs` scoping semantics are all documented in the schema itself. The description only adds that arguments are the same as ask_pipeworx and defers entirely on `packs`, so the baseline of 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 states a specific role (a beta build of the ask_pipeworx universal router over 7,556 tools) and explicitly frames it as identical to the stable router in arguments and response shape. That distinguishes it from its siblings, which are all `ask_pipeworx_beta` variants scoped to individual data packs, though it never spells out in plain terms that it answers a natural-language question by selecting and invoking a tool.

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 a clear selection rule: 'Use it exactly like ask_pipeworx when you want the newest routing,' and names the alternative (the stable router) that results are compared against. It even states the present condition — no candidate is active, so it currently matches ask_pipeworx exactly — which is honest guidance, but it stops short of telling the agent when to prefer the stable router instead.

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.