Skip to main content
Glama

Koncerty w Polsce / Concerts in Poland

search_concerts
Read-onlyIdempotent

Kto gra w moim mieście i kiedy? Nadchodzące koncerty w Polsce z GoGiga, od wielkich tras po małe kluby. / Upcoming concerts in Poland from GoGiga: big tours and small club gigs. Filter by town, dates, genre, price or text (a band, a title or a venue). 12 concerts a page, soonest first (best match first for a text query). Every concert has its GoGiga page (url) with ticket links; share that url with the user.

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_concerts"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoPolish town, e.g. "Kraków", "Wrocław", "Gdynia"
pageNoPage of results, 1 by default
genreNoA main genre (Rock & Alternative, Electronic & Dance, Hip-Hop & Rap, Reggae, Jazz, Classical, Metal & Punk, Pop, Blues, RnB & Soul) or a subgenre, e.g. "Punk"
queryNoA band, a title or a venue, e.g. "Kult" or "Stodoła"
date_toNoLast day, YYYY-MM-DD
date_fromNoFirst day, YYYY-MM-DD in Polish time; today by default
price_maxNoOnly concerts with a known ticket price up to this many złoty
radius_kmNoAlso towns within this many km of the city

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint false), so the description earns credit for going beyond them: 12 results per page, soonest-first ordering with a best-match override for text queries, and the guarantee that every concert carries a GoGiga url with ticket links that should be surfaced to the user. It stops short of describing pagination limits or behavior on empty result sets.

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 definition is compact and front-loaded: the user-facing question, then source and scope, then filters, then result ordering and the url instruction. The Polish and English halves duplicate each other, which costs space but is a deliberate bilingual convention rather than noise. No sentence is purely filler.

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 an 8-parameter, zero-required read tool with no output schema, the description covers the essentials an agent needs: what is returned (concerts with a per-concert url), ordering, page size and the filter dimensions. It is slightly thin on pagination bounds and how a text query interacts with other filters when both are supplied, but nothing critical is missing.

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 100%, so the schema already documents city, genre, query, date range, price_max and radius_km, including the 'today by default' and 'known ticket price only' caveats. The description merely restates those filter axes in prose without adding format, precedence or combination semantics. Baseline 3 applies when the schema carries the explanatory burden.

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 names a concrete resource and scope: upcoming concerts in Poland sourced from GoGiga, covering both large tours and small club gigs, and lists the available filter axes. An agent can immediately tell this is a filtered search over a concert catalogue. It does not explicitly distinguish itself from the siblings band_concerts, get_concert or list_festivals, so it falls short of a 5.

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 rather than stated: the question form "Kto gra w moim mieście i kiedy?" and the filter list suggest broad discovery searches, and the note to share the GoGiga url with the user hints at the follow-up path via get_concert. There is no explicit when-to-use or when-not-to-use guidance, and no sibling is named as an alternative for single-band lookups or festival listings.

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