Onet

Ask Pipeworx Beta

ask_pipeworx_beta

Read-onlyIdempotent

Beta version of ask_pipeworx: identical universal router (same 7,393 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 working router, just the experimental edge.

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": "ask_pipeworx_beta"
  }
}

Input Schema

Name	Required	Description
`q`	No	Alias for question.
`ask`	No	Alias for question.
`text`	No	Alias for question.
`input`	No	Alias for question.
`packs`	No	OPTIONAL. 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).
`query`	No	Alias for question.
`prompt`	No	Alias for question.
`message`	No	Alias for question.
`question`	Yes	Your question or request in natural language. Accepts query, q, prompt, text, input, ask, message as aliases.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 19, 2026

addedInput schema / properties / packs

Added value: +{
+  "description": "OPTIONAL. 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).",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

First observedSep 24, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover safety and idempotency, and the description adds genuinely non-obvious behavior: results are compared against the stable router to decide merges, no candidate is active as of 2026-07-26, and there is no fallback path because this is a full working router. It stops short of latency or rate-limit characteristics, which matter for a live experimental endpoint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The identity-to-sibling comparison is front-loaded and the no-fallback clarification is useful, but the text repeats itself ('identical universal router' then 'currently matches ask_pipeworx exactly') and ends with flavor ('just the experimental edge') that does not add decision value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 a fully documented schema and no output schema, the description covers identity, current equivalence to the stable router, evaluation purpose, and fallback behavior. It relies on the sibling's documentation for response details, which is reasonable given the stated 'same response shape' guarantee.

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%, with aliases and the packs restriction fully documented in the schema itself, so the baseline of 3 applies. The description adds nothing about the question argument, the alias set, or pack-scoped routing, so it neither helps nor harms beyond structured data.

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 names a specific resource and its exact relationship to a sibling: a beta router with the same 7,393 tools, same arguments and same response shape as ask_pipeworx, differing only in candidate routing. An agent can tell immediately what this is and how it differs from ask_pipeworx.

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 stable alternative. What it lacks is an explicit reason to prefer the stable tool, since it also says no candidate is currently active and behavior is identical, leaving the agent to infer that either works today.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Onet tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.