Skip to main content
Glama

NS Pros MCP Gateway

nsf-awards__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": "nsf-awards__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 supplied, the description does carry useful behavioral information: candidate routing is enabled live only when under test, results are compared against the stable router, and it begins to describe fallback ('Falls back to nothing, this IS a full'), but that sentence is cut off mid-word so the fallback guarantee is never actually delivered. It also omits cost, latency, or rate-limit characteristics of a router that fans out over 7,556 tools.

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 clause is front-loaded and efficient, but the text then spends substantial length on routing-experiment internals ('results are compared against the stable router to decide what merges') that do not help an agent invoke it, and it ends truncated mid-sentence. The dangling final fragment is a structural defect, not conciseness.

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 a 100%-documented single required parameter and no output schema, the description covers identity, argument parity, and the experimental-routing rationale. What it leaves incomplete is the truncated fallback sentence and any statement of when the stable ask_pipeworx should be chosen instead, which is the decision an agent actually faces here.

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%: the question parameter, its seven aliases, and the packs scope are all fully documented in the schema, including the pack-scope fallback to full-catalog routing. The description adds nothing parameter-specific beyond 'same arguments', so a baseline 3 is appropriate.

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 gives a concrete identity: a beta variant of the ask_pipeworx universal router with the same 7,556 tools, arguments, and response shape. It explicitly anchors itself to the sibling ask_pipeworx, so an agent can tell what the tool is and how it relates to the stable version, though the actual task (routing a natural-language question to tools) is only implied via the sibling reference.

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 says 'Use it exactly like ask_pipeworx when you want the newest routing', which is a use condition, and notes results are compared against the stable router. However it also states no candidate is active, so the tool currently behaves identically to ask_pipeworx, and it never says when an agent should prefer the stable router instead — leaving the choice effectively unmade.

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.