Skip to main content
Glama

Barcelona Events

by io.github.pipeworx-io

Recent Alerts

recent_alerts
Read-onlyIdempotent

Pull fired events from your subscription feed. Returns the most recent alerts the evaluator has written to your persisted feed — each carries source, citation_uri (pipeworx:// when available), and the raw event payload. Filter by type (e.g. "sec_8k") and/or since (ISO timestamp). Set mark_read:true to flag returned events read so the next call only shows newer ones. Polls work fine; the same feed is also at GET registry.pipeworx.io/alerts.json for scripts and dashboards.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoOptional — filter to one subscription type.
limitNoMax events to return (1-200, default 50).
sinceNoOptional ISO timestamp — return events fired_at >= this time.
mark_readNoFlag the returned events read in the same call (default false).
unread_onlyNoReturn only events where read_at is null (default false).

TDQS

A4/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, destructiveHint=false. The description adds behavioral context: setting mark_read:true flags events as read, affecting subsequent calls. It also mentions the alternative HTTP endpoint. This goes beyond annotations without contradicting them.

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 a single paragraph but is well-structured: it starts with the core action, then details return fields, filtering, mark_read behavior, and an alternative access method. Every sentence provides useful information without 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?

Although there is no output schema, the description explains what is returned (source, citation_uri, raw payload). It covers all parameters and gives practical usage hints. For a query tool with good annotations, this is sufficient context for agent selection and invocation.

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?

All 5 parameters have descriptions in the schema (100% coverage). The description adds extra context: explains that 'since' expects ISO timestamp, and 'mark_read' flags events as read to influence future calls. This adds meaningful behavior beyond the schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it pulls fired events from a subscription feed and returns recent alerts with specific fields (source, citation_uri, raw payload). It distinguishes itself by focusing on alert events from the subscription feed, but does not explicitly differentiate from similar sibling tools like 'events'.

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 provides usage guidance: it mentions that polling works fine and points to an alternative URL for scripts/dashboards. It explains filtering options (type, since) and the mark_read behavior, but does not explicitly say when not to use this tool.

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