Skip to main content
Glama

NS Pros MCP Gateway

noirlab-datalab__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": "noirlab-datalab__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.7/5.0
Behavior3/5

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

No annotations exist, so the description carries full burden. It does disclose genuinely useful behavior: candidate routing is enabled live under test, currently none is active, and outputs are compared against the stable router. However it says nothing about latency, reliability, cost, or any downside of choosing a shifting beta router, and the final sentence is truncated ('Falls back to nothing, this IS a full'), leaving a behavioral claim dangling.

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 identity and when-to-use clause are front-loaded and efficient, but the parenthetical repetition of 'same 7,556 tools, same arguments, same response shape' is verbose and the description terminates mid-sentence, which is a structural defect 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 9-parameter router with no annotations and no output schema, the definition covers routing behavior and the relationship to its siblings reasonably well, and the schema covers parameters. But the truncated ending drops at least one piece of stated behavior, and there is no guidance on answer provenance or how the beta's shifting routing could affect reproducibility.

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%: every alias and the packs parameter are thoroughly documented in the schema, including fallback semantics via _meta.pack_scope. The description only asserts 'same arguments' and adds no extra meaning about the question or packs parameters, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb+resource: a 'universal router' answering natural-language questions over a fixed 7,556-tool catalog. It explicitly positions itself against the stable sibling ('identical ... to ask_pipeworx', 'Use it exactly like ask_pipeworx'), so an agent can distinguish beta vs stable routing without opening either schema.

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 concrete selection condition: use this when you want the newest routing, with results compared against the stable router. It also notes no candidate is currently active, so right now it behaves identically to ask_pipeworx. What is missing is an explicit when-NOT (i.e., prefer the stable sibling for production/reproducible answers), which is only implied.

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.