Skip to main content
Glama

Konzerte suchen

search_concerts
Read-only

Upcoming events on the Upper and High Rhine in Germany, France and Switzerland, sorted by date and time: concerts and, where public, other kinds (kind and category in each result: concert, cabaret, theater, show, spoken, kids). A word for a kind or category in search ("kabarett", "lesung", "konzert") filters by it. region is one of basel (Basel and surroundings), hochrhein (High Rhine: Waldshut, Bad Säckingen, Laufenburg, Zurzach), freiburg (Freiburg and southern Baden), ortenau, karlsruhe (Karlsruhe and Baden-Baden) or elsass (Alsace: Mulhouse, Colmar, Strasbourg, northern Alsace). All arguments are optional: from/to (dates), region, genre and search (artist, venue, city, genre or region, in German, French or English; every word must match, in any order, so several words narrow the result down, at most eight count; plurals and other word forms match, "tributes" finds "Tribute"; "tribute" finds tribute shows; typos and missing accents are tolerated). Times are in UTC; if the venue's times_are_doors is true, the time is when doors open. At most 100 per call, page with limit and offset. page_url is the link to give to users: the concert's page on Trisonia, which also has the ticket link.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "input": "<input>"
    },
    "name": "search_concerts"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
limitNoThe maximum number of records to return in one page
offsetNoThe number of records to skip. Pass the `next_offset` from a previous page to fetch the following page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / input / properties / region / enum
      Previous value: -[
      -  "basel",
      -  "freiburg",
      -  "ortenau",
      -  "karlsruhe",
      -  "elsass"
      -]New value: +[
      +  "basel",
      +  "hochrhein",
      +  "freiburg",
      +  "ortenau",
      +  "karlsruhe",
      +  "elsass"
      +]
  2. First observed

TDQS

A4/5.0
Behavior5/5

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

Beyond the annotations (readOnly, non-destructive, closed-world), the description discloses result ordering ('sorted by date and time'), a hard cap of 100 per call with limit/offset paging, that returned times are UTC and may be door times when `times_are_doors` is true, and that `page_url` is the link to hand to users. It also spells out matcher behavior: every word must match in any order, at most eight count, plurals/typos/accents tolerated.

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?

The purpose and scope are front-loaded, and there is little filler — nearly every clause carries operational information. It is a single dense run-on paragraph, though, with parameter semantics, result-field semantics and matching rules interleaved rather than structured.

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 no output schema, the description carries return-value explanation and does so partly (kind/category, times_are_doors, page_url), which is the right call for a search tool. The remaining holes — undocumented `venue_key` and `genres` — are real but narrow for an otherwise thorough definition.

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?

Schema coverage is only 67% and the parameters are nested, but the description compensates well for `region` (parenthetically defining all six values) and `search` (matching rules, language support, word-count limit) and explains `from`/`to`. The gaps are `venue_key`, never mentioned anywhere, and `genres` (plural), which is undocumented while only the singular `genre` is named.

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?

The description states a specific verb and resource plus geographic scope: 'Upcoming events on the Upper and High Rhine in Germany, France and Switzerland,' with a note that it covers concerts and other public event kinds. An agent can tell this is a list/search over many events rather than a single-record lookup, which implicitly separates it from get_concert and list_venues, though no sibling is named.

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 says 'All arguments are optional,' telling the agent an unfiltered call is valid, and it explains that a kind word placed in `search` filters by kind. However, it never states when to prefer this tool over get_concert or list_venues, nor when not to use it, leaving the routing decision to inference.

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