Skip to main content
Glama

NS Pros MCP Gateway

noaa-ncei__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": "noaa-ncei__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 behavioral burden. It does disclose meaningful traits: full-catalog routing, live candidate toggling, and that results feed a merge decision. But it omits key operational behavior such as latency, cost, tier limits, and what the response actually contains, and the final sentence is truncated mid-clause ('this IS a full'), leaving the fallback claim incomplete.

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 (beta of an identical router, currently matching stable) is front-loaded, but it is restated three times in slightly different words ('identical ... same arguments ... currently matches ... exactly'). The description also ends mid-sentence, which is a real structural defect rather than a stylistic quibble.

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?

Nine parameters reduce to one substantive argument plus aliases and a pack filter, all fully described in the schema, and there is no output schema to compensate for. The description should therefore explain the routing result and behavior; it only asserts 'same response shape' without saying what that shape is, and the truncation leaves the fallback statement unresolved.

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% and the schema already documents the question parameter, its seven aliases, and the pack scope parameter in detail. The description adds nothing about argument semantics beyond noting 'same arguments' as ask_pipeworx, so it earns only the baseline for a fully documented schema.

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 identifies the tool as a beta of the universal router and states concretely that it has the same 7,556 tools, arguments, and response shape as ask_pipeworx, with candidate routing improvements toggled on during tests. It also discloses the current state (no active candidate, so identical to the stable router), which keeps an agent from selecting it under a false expectation of difference. It never quite says in a single clean clause that it answers a natural-language question by routing, but the sibling relationship is unmistakable.

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 explicitly routes selection against the sibling: 'Use it exactly like ask_pipeworx when you want the newest routing,' and explains the comparison against the stable router that decides merges. The caveat that no candidate is currently active effectively tells the agent there is no reason to prefer beta right now, which is useful decision context. No explicit when-not or prerequisite guidance (auth, latency, cost) is given.

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.