Skip to main content
Glama
Sign In

gigstamp

by uk.co.gigstamp
OverviewDiscussionsAdmin

list_venues

List the venues gigstamp tracks in a supported city, from small independent rooms to the city's larger touring venues. Each carries a scale (grassroots|major).

Input Schema

NameRequiredDescriptionDefault
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

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+]
  2. 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"
+]
  3. 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"
+]
  4. 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"
+]
  5. 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"
+]
  6. First observed

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does convey that this is a read-style enumeration and that each venue carries a scale of grassroots or major. It does not say whether all venues are returned, whether results are paginated or ordered, or what happens for an empty city.

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?

Two short sentences, front-loaded with the action and scope, then the return characteristics. Nothing redundant.

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 single-parameter, read-only listing with no output schema and full schema coverage, the description covers the essential contract, including the shape of returned items. Pagination/ordering behavior is the only notable gap.

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% and the sole parameter is a documented enum, so the schema does the heavy lifting. The description's phrase 'a supported city' merely reinforces the constraint without adding format or selection guidance beyond the schema.

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 ('List') and resource ('the venues gigstamp tracks') plus a scoping constraint ('in a supported city'), and it explicitly names the shape of the returned data (grassroots|major scale). An agent can distinguish this from list_cities and search_gigs_and_events on the resource alone.

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?

Usage is implied: a city is required and only supported cities are allowed. But the description never says when to prefer this over search_gigs_and_events or list_cities, and offers no exclusions or prerequisites.

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

All gigstamp 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