Skip to main content
Glama

Barcelona Events

by io.github.pipeworx-io

Events

events
Read-onlyIdempotent

Find upcoming cultural events & activities in Barcelona, Spain. Filter by keyword, district (e.g. "Eixample", "Ciutat Vella", "Gràcia") and date window. Returns events with venue, district, coordinates and dates. Content is in Catalan/Spanish.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoInclude events starting on/before this date YYYY-MM-DD.
fromNoInclude events ending on/after this date YYYY-MM-DD (default: today).
limitNoMax events (1-50, default 20).
queryNoKeyword over title and description, e.g. "música", "exposició", "infantil".
offsetNoPagination offset (default 0).
districtNoFilter by district, e.g. "Eixample", "Ciutat Vella", "Gràcia", "Sant Martí".

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive. Description adds valuable detail about return fields (venue, district, coordinates, dates) and content language (Catalan/Spanish), going beyond annotations.

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?

Two efficiently crafted sentences: first defines purpose and filters, second specifies output content. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, but description partially compensates by listing return fields. Missing details on pagination (offset) and potential response structure. Adequate but not fully complete.

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 coverage is 100%, so each parameter is described. Description reinforces main filters but adds little beyond schema. Baseline 3 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 states the tool finds upcoming cultural events in Barcelona with filtering by keyword, district, and date window. Distinguishes from siblings as no other tool handles this specific function.

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?

Provides clear context on when to use (filtering events by keyword, district, date) but does not explicitly state when not to use or mention alternative tools. Sibling list shows no direct competitors, so implicit differentiation is adequate.

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