Skip to main content
Glama

Madrid Events

by io.github.pipeworx-io

Events

events
Read-onlyIdempotent

Find cultural events & activities in Madrid, Spain (next ~100 days). Filter by keyword, free admission, and date window. Returns events with venue, address, geo, audience and price. Content is in Spanish.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoInclude events starting on/before this date YYYY-MM-DD.
fromNoInclude events on/after this date YYYY-MM-DD (default: today).
limitNoMax events (1-50, default 20).
queryNoKeyword over title, description and venue, e.g. "música", "exposición", "teatro".
offsetNoPagination offset (default 0).
free_onlyNoIf true, only free events.

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false. The description adds valuable behavioral context beyond annotations: the default temporal scope (next ~100 days), the Spanish content, and the specific return fields (venue, address, geo, audience, price). No contradiction with 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?

The description is two sentences, front-loaded with the primary purpose, and contains no filler. Every sentence adds informational value, making it highly efficient.

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 read-only search tool with complete schema descriptions and strong annotations, the description adequately covers scope, filters, output fields, and language. No output schema exists, but the description explicitly lists the return fields, making it self-contained.

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%, with each parameter fully described. The description only summarizes filters (keyword, free admission, date window) without adding syntax or format details beyond the schema, so it meets the baseline of 3.

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 uses a specific verb 'Find' with a clear resource: 'cultural events & activities in Madrid, Spain (next ~100 days)'. It distinguishes this tool from sibling tools, which are all research or subscription-related, by uniquely targeting events in Madrid.

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 clear context: geographic scope (Madrid), time horizon (next ~100 days), and filter options (keyword, free admission, date window). It does not explicitly state when not to use it or list alternatives, but no sibling offers similar functionality, so the guidance is adequate.

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