Skip to main content
Glama

Worms

by io.github.pipeworx-io

Ask Pipeworx Beta

ask_pipeworx_beta
Read-onlyIdempotent

Beta version of ask_pipeworx: identical universal router (same 5,738 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.6/5.0
Behavior5/5

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

The description explicitly discloses the beta behavior: candidate routing improvements are enabled live, no candidate is active right now, current behavior exactly matches ask_pipeworx, and there is no degraded fallback. This adds real context beyond the readOnly/openWorld/idempotent annotations.

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 long but information-dense, with the beta identity front-loaded and the current candidate state, usage instruction, and fallback behavior each earning their place. The retired-candidate date is a small extra detail but not padding.

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?

Given that this is expected to behave identically to ask_pipeworx, the description covers the experimental status, current equivalence, routing comparison purpose, and full functionality. No output schema exists, but response shape is tied to the sibling tool, and the remaining invocation contract is fully captured by schema and annotations.

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% and the question parameter plus all five aliases are documented. The description mentions 'same arguments' but adds no new meaning beyond the schema, so the baseline 3 is appropriate.

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?

Clearly identifies itself as the beta variant of ask_pipeworx and as a universal router with the same 5,724 tools, arguments, and response shape, while distinguishing itself from ask_pipeworx via experimental routing. The verb, resource, and relationship to its sibling are all explicit.

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?

Gives a direct instruction: use it exactly like ask_pipeworx when the newest routing is desired. It also clarifies that results are compared against the stable router, that it currently matches ask_pipeworx, and that it is not a fallback stub but a fully working router.

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

All Worms 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.6/5.0
Disambiguation2/5

Several tools have functionally overlapping purposes, most notably ask_pipeworx and ask_pipeworx_beta, which currently behave identically. The many prediction-market tools are each distinct but still leave boundaries that require careful reading, and the query/research tools (ask_pipeworx, deep_research, potentially validate_claim) have an ease of being confused. Fine verbal descriptions reduce but do not eliminate the ambiguity for an agent.

Naming Consistency3/5

All names are lowercase snake_case and many follow a verb_noun pattern, such as resolve_entity, get_classification, and list_subscriptions. However, the set is inconsistent overall: it mixes single verbs (remember, forget, subscribe), noun-style names (entity_profile, recent_alerts), and several prefixed families (pipeworx_*, polymarket_*). It's readable but not a coherent, uniformly applied convention throughout.

Tool Count2/5

34 tools in one server is well beyond the generally well-scoped 3–15 range. The server appears to bundle several unrelated domains together—WoRMS taxonomy, Pipeworx data research, Polymarket analysis, memory utilities, and subscriptions—creating avoidable cognitive load and making selection more difficult. Splitting into targeted servers would greatly improve the interface.

Completeness2/5

The server is named 'Worms' and includes a WoRMS taxonomy subdomain, but that subdomain only supports searching, classification, and common names—the rest of the marine taxonomy surface is missing (e.g., direct AphiaID record lookup, distributions, synonyms, hierarchical children). The remainder of the tools serve an entirely different data-research purpose, so the server is incomplete relative to its name AND the bundled extra domains add confusion rather than a coherent cohesive coverage.

Resources