Skip to main content
Glama

Barcelona Events

by io.github.pipeworx-io

Pipeworx Trending

pipeworx_trending
Read-onlyIdempotent

What other AI agents are calling on Pipeworx right now. Returns the top tools, top packs, and total call volume over a recent window (24h, 7d, or 30d). Useful for: (1) discovering what data sources are hot for current events, (2) confirming a popular tool is the canonical choice before asking your own question, (3) seeing whether your use case aligns with what most agents need. Self-aggregating signal — derived from CF analytics-engine, no PII, just (pack, tool, count). Cached 5min-1h depending on window.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
windowNo24h (default) | 7d | 30d. Shorter windows surface what's hot right now; longer windows show steady-state demand.

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. Description adds valuable context: data source (CF analytics-engine), privacy (no PII), and caching behavior (5min-1h). No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Concise: one sentence summary, followed by bullet-like use cases, then additional details. Every sentence adds value with no redundancy.

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?

Given no output schema, description hints at return shape (top tools, top packs, total call volume). Covers caching and data origins. Sufficient for a simple read tool with one optional parameter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% for the single parameter. Description adds meaning by explaining the trade-off between short and long windows ('surface what's hot right now' vs 'show steady-state demand'), going beyond raw enum values.

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?

Description clearly states what the tool does: 'Returns the top tools, top packs, and total call volume over a recent window.' It uses a specific verb ('returns') and resource ('top tools, top packs, total call volume'), and distinguishes from siblings like 'discover_tools' by focusing on trending data.

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?

Explicitly lists three use cases and explains the difference between window sizes. Lacks explicit when-not-to-use or alternatives, but for a simple read tool, the use cases are clear enough.

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

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

Many tools overlap heavily: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, and validate_claim all answer factual queries with subtle differences, and the Polymarket suite (bet_research, polymarket_edges, polymarket_arbitrage, polymarket_fill_risk, polymarket_edge_tracker) has fine-grained distinctions that are hard to separate. The single Barcelona events tool is isolated and unrelated to the rest, adding to agent confusion.

Naming Consistency3/5

Most tool names use snake_case and many follow a verb_noun pattern, but there are notable inconsistencies: noun-first names (entity_profile, polymarket_arbitrage, pipeworx_trending) and modifiers like beta/grounded on ask_pipeworx introduce non-uniformity. Overall the set is readable but not consistently predictable.

Tool Count2/5

With 32 tools, the set is beyond the well-scoped 3-15 range. The count is especially inappropriate for a server named 'Barcelona Events' because only one tool actually relates to Barcelona events; the other 31 are a broad data-research and utility collection with no clear connection to the server's apparent purpose.

Completeness1/5

For a server named 'Barcelona Events', the surface is severely incomplete: it offers a single events search tool with no create, update, delete, detail, venue, or organizer operations. Even interpreting the domain broadly, the mismatch between the server name and the tool set leaves a critical gap between user expectation and actual capability.

Resources