Skip to main content
Glama
Sign In

Opentreeoflife

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Ask Pipeworx Beta

ask_pipeworx_beta
Read-onlyIdempotent

Beta version of ask_pipeworx: identical universal router (same 7,190 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

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. Changed1 schema field changed
    • 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"
+}
  2. Changed4 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "question": "What is the current US unemployment rate?"
+  }
+]
    • addedInput schema / properties / ask
      Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}
    • addedInput schema / properties / message
      Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}
    • changedInput schema / properties / question / description
      Previous value: -"Your question or request in natural language. Accepts query, q, prompt, text, input as aliases."New value: +"Your question or request in natural language. Accepts query, q, prompt, text, input, ask, message as aliases."
  3. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, open-world and non-destructive behavior, so the safety profile is covered. The description adds process context — results are compared against the stable router to decide merges, the last candidate was retired on 2026-07-26, and there is no downstream fallback — but says little about what the call actually returns or how routing metadata is surfaced.

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 key facts (beta router, currently identical to stable, no fallback) are front-loaded, but the description is padded with a retirement date, a parenthetical about candidate status, and the 'just the experimental edge' flourish that do not help an agent decide or invoke.

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 routing tool with no output schema, the description should say what comes back, yet it only asserts the 'same response shape' as a sibling the agent may not have called. The pack-scope behavior is documented in the schema, but the response contract remains an inference.

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 every alias and the packs parameter fully documented in the schema, so the description adds nothing about parameters beyond 'same arguments'. With 9 parameters where 8 are aliases of question, the schema does the work and baseline 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 frames the tool as a 'universal router' over the same 7,190 tools as ask_pipeworx and implies it takes a natural-language question and routes it to the best-matching tool. It distinguishes itself from the stable sibling by being the experimental edge, though it never states the core action in a plain verb+resource sentence and leans on 'identical to ask_pipeworx' to carry the meaning.

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 direct usage rule — 'Use it exactly like ask_pipeworx when you want the newest routing' — and clarifies there is no fallback, so the agent knows the tool is self-sufficient. It does not say when to prefer the stable ask_pipeworx instead, and the admission that no candidate is active right now undercuts the reason to choose this at all.

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

All Opentreeoflife toolsInspect
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.

Resources