Skip to main content
Glama

Kiedy i gdzie gra wykonawca / Artist tour dates

artist_tour
Read-onlyIdempotent

Kiedy i gdzie zagra ten wykonawca w Polsce? Wszystkie nadchodzące terminy jednego wykonawcy z KiedyKoncert.pl. / When and where does this artist play in Poland? All upcoming concert dates of one artist or band listed on KiedyKoncert.pl, with the artist page link and each concert page link. Typos are tolerated; if the name is ambiguous, candidates are returned. A festival or tour name without such an artist returns upcoming concerts with that title (status found_by_title).

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": {
      "artist": "<artist>"
    },
    "name": "artist_tour"
  }
}

Input Schema

NameRequiredDescriptionDefault
artistYesArtist or band name, e.g. "Dawid Kwiatkowski". / Nazwa wykonawcy.

Output Schema

NameRequiredDescriptionDefault
okYes
noteNoGuidance for answering, e.g. when nothing was found.
queryNo
artistNo
statusYes
messageNo
concertsNo
returnedNo
browse_urlNoKiedyKoncert.pl page to browse (full list, also when nothing was found).
candidatesNo
search_hintNoWhere to look on KiedyKoncert.pl when nothing matched.
total_foundNo
interpreted_asNoName used after correcting a typo.
upcoming_countNoUpcoming dates excluding cancelled ones.
cancelled_countNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / status / enum
      Previous value: -[
      -  "found",
      -  "no_upcoming",
      -  "artist_not_found",
      -  "ambiguous_artist",
      -  "missing_input",
      -  "invalid_request",
      -  "temporary_error"
      -]New value: +[
      +  "found",
      +  "found_by_title",
      +  "no_upcoming",
      +  "artist_not_found",
      +  "ambiguous_artist",
      +  "missing_input",
      +  "invalid_request",
      +  "temporary_error"
      +]
  2. Changed1 schema field changed
    • changedOutput schema / properties / status / enum
      Previous value: -[
      -  "found",
      -  "no_upcoming",
      -  "artist_not_found",
      -  "ambiguous_artist",
      -  "invalid_request",
      -  "temporary_error"
      -]New value: +[
      +  "found",
      +  "no_upcoming",
      +  "artist_not_found",
      +  "ambiguous_artist",
      +  "missing_input",
      +  "invalid_request",
      +  "temporary_error"
      +]
  3. Changed2 schema fields changed
    • addedOutput schema / properties / browse_url
      Added value: +{
      +  "description": "KiedyKoncert.pl page to browse (full list, also when nothing was found).",
      +  "type": "string"
      +}
    • addedOutput schema / properties / search_hint
      Added value: +{
      +  "description": "Where to look on KiedyKoncert.pl when nothing matched.",
      +  "type": "string"
      +}
  4. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare this a safe, idempotent read against a closed dataset, so the bar is lower. The description still adds real behavioral context — fuzzy matching, ambiguity candidate handling, the found_by_title status, and returned page links — that the annotations do not cover.

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 core question and scope are front-loaded, and the edge-case behavior follows compactly. The Polish/English duplication inflates length without adding information, but every substantive sentence carries weight.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read tool with full annotations and an output schema, the description covers scope, matching behavior, fallback semantics, and returned links. An agent has everything needed to call it correctly without further inference.

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?

With one required parameter and 100% schema coverage (including an example), the baseline is 3. The description earns above that by explaining how the artist string is matched: typos tolerated, ambiguous input returns multiple candidates, and non-artist titles still work.

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 specific verb and resource: upcoming concert dates for a single artist, sourced from KiedyKoncert.pl, scoped to Poland. It is far more specific than the title alone, though it never explicitly contrasts itself with siblings like search_concerts or get_concert.

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?

It clearly states the input contract (one artist/band), that typos are tolerated, that ambiguous names yield candidates, and that a festival/tour title without an artist falls back to a found_by_title search. What it lacks is an explicit when-not-to-use or a named alternative tool.

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