Skip to main content
Glama

Lobsters

by io.github.pipeworx-io

Ask Pipeworx Beta

ask_pipeworx_beta
Read-onlyIdempotent

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

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the beta status, the live candidate-routing behavior, the current absence of an active candidate, and the fact that this is a full working router rather than a fallback. This gives the agent a clear and honest picture of what to expect.

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 and current-state information are front-loaded, and each sentence adds distinct value. The exact tool count and retirement date are slightly granular, but they contribute to the transparency without feeling like filler.

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 single-question router with no output schema, the description covers current behavior, relationship to the stable tool, response-shape identity, experimental caveats, and fallback semantics. An agent has enough information to choose and invoke this tool correctly.

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?

The input schema already provides 100% description coverage for all six parameters, including the aliases for question, so the description adds little parameter-level detail. The statement that it takes the same arguments as ask_pipeworx is useful context but does not need to restate the schema.

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 immediately identifies the tool as the beta version of ask_pipeworx and explains that it is the same universal router with the same 5,767 tools, arguments, and response shape. This makes the purpose concrete and clearly separates it from the stable ask_pipeworx through the experimental routing framing.

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?

It explicitly says to use it exactly like ask_pipeworx when the newest routing is desired, and explains that results are compared against the stable router to decide what merges. The note that no candidate is currently active also tells the agent that behavior presently matches ask_pipeworx exactly, which is strong usage guidance.

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

All Lobsters 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

Many tools have overlapping purposes, e.g., three tools for querying Pipeworx data (ask_pipeworx, ask_pipeworx_grounded, deep_research), and six tools for Polymarket prediction markets. The boundaries between them are unclear, causing potential for misselection.

Naming Consistency3/5

Tool names are all snake_case but follow inconsistent patterns: some use verb_noun (get_hottest, get_newest), some are single verbs (remember, forget), and others are noun_noun (bet_research, polymarket_arbitrage). While readable, the lack of a consistent pattern adds confusion.

Tool Count2/5

With 34 tools, the server is overloaded, especially given its name 'Lobsters' suggests a focus on that site, yet only 4 tools are Lobsters-related. The majority belong to Pipeworx, Polymarket, and generic utilities, making the scope extremely broad and unfocused.

Completeness2/5

For the implied domain of Lobsters, the tool set is incomplete (missing create/update/delete). For the broader domains (Pipeworx, Polymarket), the set is extensive but doesn't align with the server's name. The lack of a coherent domain leaves obvious gaps relative to any single purpose.

Resources