Skip to main content
Glama

search_gigs_and_events

Search a supported city's upcoming live music and events: band gigs, open mics, comedy nights, jam and folk sessions, festivals, and club nights, spanning grassroots gigs at small independent venues through to major shows at the city's big rooms (listed side by side; coverage aims to be complete). Returns them most imminent first, each with a booking link out (gigstamp does not sell tickets) and a gig-page url to cite. Filter by date range, venue, district (on a city that has them, see list_cities), category, scale (grassroots, major or commercial), or free text. Only supported cities return data (see list_cities).

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": {
      "city": "<city>"
    },
    "name": "search_gigs_and_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNostarts on or before this local day, YYYY-MM-DD
cityYescity slug; supported cities: oxford, brighton, sheffield, leeds, glasgow, birmingham, liverpool, nottingham, manchester, edinburgh, london, bristol, southampton, derby, cardiff, newcastle, aberdeen, cambridge, norwich, hull, leicester, preston, belfast
fromNoon or after this local day, YYYY-MM-DD
limitNomax results (default 100)
queryNofree-text match over act / venue / summary
scaleNonarrow to grassroots (small independent venues), major (large / touring rooms) or commercial (nightclubs, chain bars and restaurants where music is incidental)
venueNovenue slug
coversNoinclude covers bands and covers nights (default true; false hides them)
categoryNo
districtNoa named district's slug, e.g. camden, on a city that has districts (list_cities gives each city's list; asking for any other is an error). A venue we cannot place is left out of a district and is in the city's whole list.
tributesNoinclude tribute acts (default false)
classicalNoinclude classical concerts (default true; false hides them)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / scale / description
      Previous value: -"narrow to grassroots (small independent venues) or major (large / touring rooms)"New value: +"narrow to grassroots (small independent venues), major (large / touring rooms) or commercial (nightclubs, chain bars and restaurants where music is incidental)"
    • changedInput schema / properties / scale / enum
      Previous value: -[
      -  "grassroots",
      -  "major"
      -]New value: +[
      +  "grassroots",
      +  "major",
      +  "commercial"
      +]
  2. Changed2 schema fields changed
    • changedInput schema / properties / city / description
      Previous value: -"city slug; supported cities: oxford, brighton, sheffield, leeds, glasgow, birmingham, liverpool, nottingham, manchester, edinburgh, bristol, southampton, derby, cardiff, newcastle, aberdeen, cambridge, norwich, hull, leicester, preston, belfast"New value: +"city slug; supported cities: oxford, brighton, sheffield, leeds, glasgow, birmingham, liverpool, nottingham, manchester, edinburgh, london, bristol, southampton, derby, cardiff, newcastle, aberdeen, cambridge, norwich, hull, leicester, preston, belfast"
    • changedInput schema / properties / city / enum
      Previous value: -[
      -  "oxford",
      -  "brighton",
      -  "sheffield",
      -  "leeds",
      -  "glasgow",
      -  "birmingham",
      -  "liverpool",
      -  "nottingham",
      -  "manchester",
      -  "edinburgh",
      -  "bristol",
      -  "southampton",
      -  "derby",
      -  "cardiff",
      -  "newcastle",
      -  "aberdeen",
      -  "cambridge",
      -  "norwich",
      -  "hull",
      -  "leicester",
      -  "preston",
      -  "belfast"
      -]New value: +[
      +  "oxford",
      +  "brighton",
      +  "sheffield",
      +  "leeds",
      +  "glasgow",
      +  "birmingham",
      +  "liverpool",
      +  "nottingham",
      +  "manchester",
      +  "edinburgh",
      +  "london",
      +  "bristol",
      +  "southampton",
      +  "derby",
      +  "cardiff",
      +  "newcastle",
      +  "aberdeen",
      +  "cambridge",
      +  "norwich",
      +  "hull",
      +  "leicester",
      +  "preston",
      +  "belfast"
      +]
  3. Changed1 schema field changed
    • addedInput schema / properties / district
      Added value: +{
      +  "description": "a named district's slug, e.g. camden, on a city that has districts (list_cities gives each city's list; asking for any other is an error). A venue we cannot place is left out of a district and is in the city's whole list.",
      +  "type": "string"
      +}
  4. Changed2 schema fields changed
    • changedInput schema / properties / city / description
      Previous value: -"city slug; supported cities: oxford, brighton, sheffield, leeds, glasgow"New value: +"city slug; supported cities: oxford, brighton, sheffield, leeds, glasgow, birmingham, liverpool, nottingham, manchester, edinburgh, bristol, southampton, derby, cardiff, newcastle, aberdeen, cambridge, norwich, hull, leicester, preston, belfast"
    • changedInput schema / properties / city / enum
      Previous value: -[
      -  "oxford",
      -  "brighton",
      -  "sheffield",
      -  "leeds",
      -  "glasgow"
      -]New value: +[
      +  "oxford",
      +  "brighton",
      +  "sheffield",
      +  "leeds",
      +  "glasgow",
      +  "birmingham",
      +  "liverpool",
      +  "nottingham",
      +  "manchester",
      +  "edinburgh",
      +  "bristol",
      +  "southampton",
      +  "derby",
      +  "cardiff",
      +  "newcastle",
      +  "aberdeen",
      +  "cambridge",
      +  "norwich",
      +  "hull",
      +  "leicester",
      +  "preston",
      +  "belfast"
      +]
  5. Changed2 schema fields changed
    • changedInput schema / properties / city / description
      Previous value: -"city slug; supported cities: oxford, brighton, sheffield, leeds"New value: +"city slug; supported cities: oxford, brighton, sheffield, leeds, glasgow"
    • changedInput schema / properties / city / enum
      Previous value: -[
      -  "oxford",
      -  "brighton",
      -  "sheffield",
      -  "leeds"
      -]New value: +[
      +  "oxford",
      +  "brighton",
      +  "sheffield",
      +  "leeds",
      +  "glasgow"
      +]
  6. Changed2 schema fields changed
    • changedInput schema / properties / city / description
      Previous value: -"city slug; supported cities: oxford, brighton, sheffield"New value: +"city slug; supported cities: oxford, brighton, sheffield, leeds"
    • changedInput schema / properties / city / enum
      Previous value: -[
      -  "oxford",
      -  "brighton",
      -  "sheffield"
      -]New value: +[
      +  "oxford",
      +  "brighton",
      +  "sheffield",
      +  "leeds"
      +]
  7. Changed2 schema fields changed
    • changedInput schema / properties / category / enum
      Previous value: -[
      -  "original",
      -  "tribute",
      -  "classical",
      -  "comedy",
      -  "openMic",
      -  "jamSession",
      -  "folkSession",
      -  "festival",
      -  "event"
      -]New value: +[
      +  "original",
      +  "tribute",
      +  "classical",
      +  "covers",
      +  "comedy",
      +  "openMic",
      +  "jamSession",
      +  "folkSession",
      +  "festival",
      +  "event"
      +]
    • addedInput schema / properties / covers
      Added value: +{
      +  "description": "include covers bands and covers nights (default true; false hides them)",
      +  "type": "boolean"
      +}
  8. Changed2 schema fields changed
    • changedInput schema / properties / city / description
      Previous value: -"city slug; supported cities: oxford, brighton"New value: +"city slug; supported cities: oxford, brighton, sheffield"
    • changedInput schema / properties / city / enum
      Previous value: -[
      -  "oxford",
      -  "brighton"
      -]New value: +[
      +  "oxford",
      +  "brighton",
      +  "sheffield"
      +]
  9. Changed2 schema fields changed
    • changedInput schema / properties / category / enum
      Previous value: -[
      -  "original",
      -  "tribute",
      -  "comedy",
      -  "openMic",
      -  "jamSession",
      -  "folkSession",
      -  "festival",
      -  "event"
      -]New value: +[
      +  "original",
      +  "tribute",
      +  "classical",
      +  "comedy",
      +  "openMic",
      +  "jamSession",
      +  "folkSession",
      +  "festival",
      +  "event"
      +]
    • addedInput schema / properties / classical
      Added value: +{
      +  "description": "include classical concerts (default true; false hides them)",
      +  "type": "boolean"
      +}
  10. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses sort order ('most imminent first'), that each result carries a booking link out ('gigstamp does not sell tickets') and a gig-page url to cite, and that coverage aims to be complete with grassroots and major shows listed side by side. It omits pagination/result-count behavior beyond the limit param and any failure modes beyond the district error.

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?

Front-loaded with purpose and output shape before filters, and every clause is informative. There is mild redundancy: the scale taxonomy is explained twice and the long genre list is partly re-enumerated by the category filter.

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?

For a 12-parameter, no-annotation, no-output-schema search tool, the description covers scope, sort order, result contents, city gating, and the district edge case, which is enough to call it correctly. It could go slightly further on result volume/pagination expectations.

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 92%, so the schema already explains every parameter including defaults. The description adds little beyond it: it restates the filter set (date range, venue, district, category, scale, free text) and adds one genuinely useful note that district only works on cities that have them (see list_cities). Baseline 3 applies.

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?

States a specific verb and resource ('Search a supported city's upcoming live music and events') with an explicit enumeration of what counts (gigs, open mics, comedy, jam/folk sessions, festivals, club nights) and the grassroots-to-major scale range. This is clearly distinguishable from get_gig (single gig detail) and list_venues.

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?

Explicitly bounds usage with 'Only supported cities return data (see list_cities)' and warns that requesting a district on a city without districts 'is an error', routing the agent to list_cities first. It doesn't explicitly say when to switch to get_gig for detail, which keeps it below a 5.

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