Skip to main content
Glama
Sign In

KiedyKoncert.pl

by pl.kiedykoncert
OverviewDiscussionsAdmin

Kto gra w Twoim mieście i kiedy / Concerts in Poland

search_concerts
Read-onlyIdempotent

Kto gra w moim mieście w ten weekend? Gdzie i kiedy zagra mój wykonawca? Nadchodzące koncerty w Polsce z KiedyKoncert.pl po wykonawcy (literówki są tolerowane), miejscowości z promieniem, datach i gatunku. / Who is playing in my city this weekend, and when does my artist play? Upcoming concerts in Poland listed on KiedyKoncert.pl. Filters: artist, band, festival or show name (typos tolerated); Polish locality with radius; dates or a when shortcut; genre. Returns up to 20 concerts per call (page further with offset/next_offset): date, time, city, venue, price from, status incl. cancelled and the concert page link, plus the total number of matches and browse_url with the full list. Default range: next 60 days; with artist and no dates: all announced dates.

Input Schema

NameRequiredDescriptionDefault
cityNoPolish city, town or village in nominative case, e.g. "Kraków"; for a village name used in many places add the municipality, e.g. "Nowa Wieś, gm. Bircza". / Miejscowość w Polsce.
whenNoDate shortcut computed in Europe/Warsaw; this_weekend = Friday-Sunday. Overrides date_from/date_to.
genreNoGenre slug or Polish name, e.g. rap, rock, pop, jazz, metal, classical, electronic, disco-polo (see list_genres). / Gatunek.
limitNoMaximum concerts to return (1-20, default 10).
artistNoArtist, band, festival or show name, e.g. "Dawid Kwiatkowski". / Wykonawca, zespół lub nazwa wydarzenia.
offsetNoSkip this many matches (paging); use next_offset from the previous result. / Przesunięcie listy.
date_toNoLast day, YYYY-MM-DD (inclusive).
date_fromNoFirst day, YYYY-MM-DD (default today).
radius_kmNoSearch radius around the city in km (10-100, default 30).

Output Schema

NameRequiredDescriptionDefault
okYes
cityNo
noteNoGuidance for answering, e.g. when nothing was found.
genreNo
queryNoFilters as applied.
offsetNoOffset applied (only when > 0).
statusYes
messageNo
concertsNo
returnedNo
browse_urlNoKiedyKoncert.pl page with the full list.
candidatesNo
next_offsetNoPresent when more matches exist: pass as offset to get the next page.
search_hintNoWhere to look on KiedyKoncert.pl when nothing matched.
total_foundNo
interpreted_asNoName used after correcting a typo.
matched_artistsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / search_hint
      Added value: +{
+  "description": "Where to look on KiedyKoncert.pl when nothing matched.",
+  "type": "string"
+}
  2. First observed

TDQS

A3.8/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds substantial beyond-schema behavior: page size cap of 20 with offset/next_offset paging, total match count and browse_url in the response, cancelled statuses included, typo tolerance on artist names, and the 60-day default window. These are exactly the operational traits an agent needs before calling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The filter list and return summary are front-loaded and useful, but the definition is bilingual and says the same thing twice in Polish and English, roughly doubling length without adding information. The result-cap, paging and default-range clauses are buried after the duplication.

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 nine optional parameters, an output schema and full schema descriptions, the definition covers the remaining gaps an agent needs: defaults, paging, result caps and typo tolerance. The missing piece is positioning relative to the tour/lookup siblings.

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, when enum, genre, limit, offset and radius. The description adds only light meaning beyond it — typos tolerated for artist, locality-with-radius combined use, and the `when` shortcut — which is the baseline for fully documented schemas.

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?

States a specific verb and resource ('Upcoming concerts in Poland listed on KiedyKoncert.pl') with the exact filter dimensions, so an agent knows precisely what it retrieves. It never mentions the sibling tools artist_tour, get_concert or list_genres, so the agent must infer the split from names 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 context is implied through examples ('Kto gra w moim mieście w ten weekend?') and defaults ('Default range: next 60 days; with artist and no dates: all announced dates'), which tells the agent how the tool behaves when inputs are omitted. However, there is no explicit statement of when to prefer this over artist_tour or get_concert.

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

All KiedyKoncert.pl 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