Skip to main content
Glama
Sign In

Odds Api

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Ask Pipeworx Beta

ask_pipeworx_beta
Read-onlyIdempotent

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

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. Changed4 schema fields changed
    • addedInput schema / properties / ask
      Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}
    • addedInput schema / properties / message
      Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}
    • 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"
+}
    • 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."
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "question": "What is the current US unemployment rate?"
+  }
+]
  3. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world, non-destructive. The description adds genuinely non-obvious behavior: candidate routers are compared against the stable router, no candidate is active as of a dated retirement, and it is a full working router rather than a fallback stub. It does not describe the response envelope or latency/rate characteristics, and with no output schema a pointer to what actually comes back is only 'same response shape as ask_pipeworx'.

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 core identity (beta mirror of ask_pipeworx) is front-loaded in the first clause, then the experimental status. It is slightly padded — the 'currently matches ask_pipeworx exactly' statement and the 'falls back to nothing / this IS a full working router' sentence restate the same point about equivalence, costing a little length for emphasis.

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 single-question router with no output schema and mostly alias parameters, the description covers identity, selection rule, experiment semantics, and non-fallback behavior. The one residual gap is that return values are only defined by reference to another tool, which assumes the agent knows ask_pipeworx's response shape.

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 eight non-required params are all documented aliases, so the schema does the heavy lifting. The description only adds 'same arguments' as ask_pipeworx and does not clarify which alias wins on conflict or add anything about `packs` beyond what the schema field already states. Baseline 3 is correct.

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 precisely what the tool is: a beta universal router with the same 7,169 tools, same arguments, and same response shape as ask_pipeworx. It names the sibling it mirrors and explains what differentiates it (live candidate routing experiments), so an agent can distinguish it from ask_pipeworx and ask_pipeworx_grounded without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit routing rule: 'Use it exactly like ask_pipeworx when you want the newest routing.' It also discloses that no candidate is currently active, so the tool presently behaves identically to ask_pipeworx — effectively telling the agent there is no benefit to choosing it right now. That is a rare and valuable when/when-not signal.

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

All Odds Api 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