Skip to main content
Glama
Sign In

GeNEVERsleep

by ch.geneversleep
OverviewDiscussionsAdmin

Search nightlife events

search_events
Read-onlyIdempotent

Find upcoming parties, club nights, concerts and festivals in Geneva, Lausanne, Nyon, French-speaking Switzerland and neighbouring France. Dates are Europe/Zurich nights. Each result has the GeNEVERsleep page (url), the original listing / ticket link and the source name: show and link both.

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
qNoFree text: artist, title or venue.
cityNogeneve (Geneva), lausanne, nyon, la-cote, france-voisine (neighbouring France: Annemasse, Annecy, Pays de Gex…), fribourg, neuchatel, valais, riviera. Omit for all.
langNoLanguage of page URLs and descriptions. Default fr.
whenNotonight | tomorrow | this_weekend | next_weekend | this_week | next_7_days (default) | YYYY-MM-DD | YYYY-MM-DD..YYYY-MM-DD (max 92 nights)
genreNotechno, house, electronic, hip-hop, rnb, jazz, rock/indie, punk, metal, reggae/dub, latin, afro, soul/funk, live music, experimental, festival, club night, queer…
limitNoDefault 10.
free_onlyNoOnly free / entrée libre / prix libre (pay what you want).
max_price_chfNoOnly events whose lowest listed CHF price is at or below this. Events without a parseable CHF price are excluded when this is set.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the read-only and idempotent annotations, the description specifies that dates are Europe/Zurich nights and identifies the per-result GeNEVERsleep URL, original listing or ticket link, and source name. The instruction to show and link both sources is useful presentation behavior, though freshness, ordering, and empty-result behavior remain unspecified.

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 compact sentences are front-loaded with purpose and scope, then add timezone and result-presentation behavior. There is no filler or repetitive recitation of the parameter list.

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?

Together with the rich schema, the description supplies enough scope, date interpretation, and output-linking information to invoke a search and present its results correctly despite the absence of an output schema. It is less complete on sibling selection and operational details such as result freshness and ordering.

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?

Although the schema already documents all eight parameters, "Dates are Europe/Zurich nights" adds important semantics for relative values such as tonight and for explicit date ranges. The geographic sentence reinforces the city scope, but most filter meanings still come from the schema rather than the description.

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?

"Find upcoming parties, club nights, concerts and festivals" supplies a specific verb, event types, and temporal scope, while the named Swiss and neighbouring-French geography tightly bounds the search. It does not explicitly distinguish this broad search from siblings such as upcoming_big_nights or get_event.

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 upcoming-nightlife focus and regional scope provide clear context for using the tool for event discovery. However, there are no explicit routing rules for choosing this tool over upcoming_big_nights, browsing list_venues, or retrieving details with get_event.

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

All GeNEVERsleep toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources