Skip to main content
Glama

Madrid Events

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.1/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds valuable context beyond annotations: it explains the live experimental status, that routing improvements are enabled whenever under test, that results are compared to the stable router, and that it is still a fully working router with no fallback.

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 most important beta context and each sentence adds useful information. It is somewhat verbose with redundant framing around matching ask_pipeworx, but it remains compact and readable.

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-parameter routing tool with rich annotations, the description covers the essential context: beta status, current equivalence to ask_pipeworx, and the comparison purpose. It references the same response shape rather than detailing it, which is acceptable given the sibling tool exists, though a bit more output-shape context would round it out.

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%, so the input schema already documents the question parameter and its aliases thoroughly. The description mentions 'same arguments' as ask_pipeworx but adds no additional semantic detail about individual parameters, so the baseline of 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?

The description clearly identifies this as the beta version of ask_pipeworx, a universal router with the same 5,743 tools, arguments, and response shape. It distinguishes itself from the stable sibling by explicitly noting no candidate is currently active, so it now matches ask_pipeworx exactly.

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 explicitly tells the agent when to use this tool ('when you want the newest routing') and names the stable alternative, ask_pipeworx. The current no-candidate state is clearly described, but it does not give a full when-not-to-use statement concerning grounded variants or other siblings.

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

All Madrid Events 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

The set contains several heavily overlapping clusters: three ask_pipeworx variants (with ask_pipeworx_beta explicitly identical to ask_pipeworx right now) and six polymarket-related tools that all orbit edge detection, arbitrage, and fill risk. An agent choosing among bet_research, polymarket_edges, polymarket_arbitrage, and polymarket_kalshi_spread would have a hard time picking the right one.

Naming Consistency3/5

Most tools use readable snake_case, so the naming is not chaotic. However, the pattern is mixed: some are verb_noun (compare_entities, resolve_entity), some are brand-style (ask_pipeworx, ask_pipeworx_beta), and some are noun-only phrases (events, polymarket_arbitrage, pipeworx_trending). It is consistent in casing but not in structural convention.

Tool Count2/5

32 tools is well beyond the usual well-scoped range, and the count is inflated by multiple near-duplicate clusters for querying, prediction markets, and memory/subscription utilities. For a server named Madrid Events, this is especially disproportionate since only one tool actually relates to Madrid events.

Completeness2/5

Relative to the Madrid Events name, the domain coverage is almost entirely missing: only events addresses the stated purpose, and it is read-only with no detail view, booking, or management operations. If interpreted as the broader Pipeworx platform, coverage is richer, but the server's stated identity makes the gap severe.

Resources