Skip to main content
Glama

Search events on sale

search_events
Read-onlyIdempotent

Public catalogue of ticketick.ch: upcoming concerts, festivals, theatre and shows in Switzerland, with dates, venues, prices, availability and booking links. No API key needed.

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: title, artist, organizer, venue, tags.
toNoUntil date (YYYY-MM-DD), inclusive.
cityNo
fromNoFrom date (YYYY-MM-DD), default today.
limitNoDefault 20.
localeNoLanguage of texts and links (default fr).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/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 the safety profile is covered. The description adds two genuinely useful behavioral facts beyond that: no authentication/API key is required, and results are limited to upcoming Switzerland events. It does not mention pagination, result ordering, or how the default limit of 20 interacts with a broad query.

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?

A single tight sentence with no wasted words, front-loaded with the source and content. It could be marginally better structured by separating the capability statement from the listing of returned fields, but nothing is superfluous.

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?

For a six-parameter, zero-required search tool with no output schema, the description does well on output content (it enumerates the fields each event carries) but leaves the retrieval contract underspecified: no word on pagination, ordering, or how to broaden a query with no filters. Adequate, not 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 description coverage is 83%, so the schema already explains q, from, to, limit and locale; the only undocumented parameter is city. The description adds no syntax, default, or interaction detail (e.g., whether q and city combine with AND semantics), so it neither compensates for the remaining gap nor adds meaning beyond the schema. Baseline 3 is appropriate.

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

Purpose3/5

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

The description identifies the resource precisely (ticketick.ch's public catalogue of concerts, festivals, theatre and shows in Switzerland) and even what each record carries (dates, venues, prices, availability, booking links). But it never states the action: it reads as a dataset blurb rather than a statement that this tool searches/filters that catalogue, and it draws no distinction from the sibling get_public_event.

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

Usage Guidelines2/5

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

"No API key needed" is access information, not usage guidance. There is no statement of when to call this versus get_public_event, no note that all filters are optional, and no hint about what happens with an empty query (i.e., whether it returns the full upcoming catalogue).

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