Skip to main content
Glama

Gdacs

by io.github.pipeworx-io

Ask Pipeworx Beta

ask_pipeworx_beta
Read-onlyIdempotent

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

TableJSON Schema
NameRequiredDescriptionDefault
qNoAlias for question.
textNoAlias for question.
inputNoAlias for question.
queryNoAlias for question.
promptNoAlias for question.
questionYesYour question or request in natural language. Accepts query, q, prompt, text, input as aliases.

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive hints. The description adds meaningful behavioral context beyond that: it is a beta/experimental edge, candidate routing changes may be live, no candidate is currently active, and there is no fallback — it is a full working router. This is highly transparent.

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 description is front-loaded with the tool's identity and current behavior, and each sentence contributes useful information. There is minor redundancy between 'Beta version', 'experimental edge', and 'currently matches ask_pipeworx exactly', but overall it is well structured and not bloated.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex universal router with no output schema, the description covers current behavior, relationship to the stable tool, and what the agent should expect. Referencing the same response shape as ask_pipeworx bridges the missing output schema. It is complete enough for confident selection and invocation.

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 six parameters and all aliases documented. The description says 'same arguments' but adds no parameter-level meaning beyond the schema. Baseline of 3 is appropriate since the schema carries the full burden.

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 clearly identifies the tool as a beta universal router that behaves identically to ask_pipeworx, with the same 5,743 tools and response shape. It also distinguishes it from the stable router by noting the experimental routing improvements. This is a specific, unambiguous purpose that an agent can act on.

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?

The description explicitly states when to use it: 'Use it exactly like ask_pipeworx when you want the newest routing.' It also notes that it currently matches ask_pipeworx exactly, which is useful context. It does not explicitly exclude cases or compare against ask_pipeworx_grounded, so it stops short of a 5.

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

All Gdacs toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.5/5.0
Disambiguation4/5

Most tools have clear, distinct purposes, but the three ask_pipeworx variants (especially ask_pipeworx_beta, identical to ask_pipeworx) and the six Polymarket tools overlap conceptually and could cause misselection. Detailed descriptions largely compensate, but the boundaries between some meta-tools (e.g., ask_pipeworx vs deep_research vs bet_research) require careful reading.

Naming Consistency3/5

All names are snake_case, but conventions are mixed: verb-first (ask_pipeworx, compare_entities, discover_tools), noun-first compounds (entity_profile, polymarket_arbitrage), and single-word nouns (event, events, rss). The pattern is predictable for common actions but inconsistent across the set, making it harder to guess names for related tasks.

Tool Count2/5

At 35 tools, the count is heavy and the server named 'Gdacs' includes many unrelated tools (Polymarket, npm scanning, AI visibility), indicating scope creep. Several tools could be consolidated (e.g., the ask_pipeworx family and multiple pattern-market scanners), and the breadth dilutes the disaster-alerting focus implied by the server name.

Completeness4/5

The surface covers core workflows: data querying (ask/research/validate), entity profiling, prediction-market analysis (arbitrage/edges/fill risk), and subscription management (create/list/cancel). Minor gaps exist, such as no direct fetch tool for a specific Pipeworx pack and limited GDACS event management (only read operations), but these are workable with the provided meta-tools.

Resources