Skip to main content
Glama

Search parties and festivals

search_events
Read-onlyIdempotent

Upcoming electronic music parties and festivals listed on Lineup Atlas (past dates are never returned). Filter by text (artist, venue, title), city, country, kind, genre and date range. Each result has its Lineup Atlas page (webUrl): link it when you use the result.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLatest start date, ISO 8601 (YYYY-MM-DD).
cityNoCity name as written locally, e.g. Berlin, Paris, Amsterdam.
fromNoEarliest start date, ISO 8601 (YYYY-MM-DD).
kindNoOnly parties (club nights) or only festivals.
genreNoOne genre of the Lineup Atlas vocabulary.
limitNoHow many results (1 to 20, default 10).
queryNoFree text: an artist, a venue, a party or festival name.
localeNoLanguage of the texts and page links (default: en).
countryNoISO 3166-1 alpha-2 country code, e.g. DE, FR, NL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds two things annotations cannot: results are strictly future-dated ('past dates are never returned') and each result carries a webUrl that the agent is asked to link — an attribution/usage rule that changes how output should be presented.

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?

Three short sentences, front-loaded with the resource and scope, then filters, then the output/webUrl obligation. No filler or restatement of the name/title alone; every clause carries information.

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?

With nine optional parameters, no output schema, and zero required fields, the definition supplies enough to call the tool correctly and even compensates for the missing output schema by naming the webUrl field. It does not cover result ordering, pagination beyond the schema's limit cap, or empty-result behavior, which keeps it short of a 5.

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 every one of the nine parameters already carries its own description, including formats (ISO 8601), ISO country codes, and the genre vocabulary. The description only enumerates the same facets at a higher level and adds no syntax or format detail beyond the schema, which is the expected baseline 3.

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?

States a specific verb and resource — parties and festivals on Lineup Atlas — and pins the scope with 'Upcoming' plus the explicit exclusion '(past dates are never returned)'. It does not name a sibling to distinguish itself from, but the entity focus (parties/festivals) is clear enough to separate it from search_artists, search_venues, and get_venue_events.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It tells the agent how to filter (text, city, country, kind, genre, date range) but never states when to choose this over siblings such as get_venue_events or get_artist_dates, nor any prerequisite or 'when not to use' condition. Usage is implied by the entity scope rather than spelled out.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources