KiedyKoncert.pl

Szczegóły koncertu / Concert details

get_concert

Read-onlyIdempotent

O której zaczyna się koncert, gdzie dokładnie i kto sprzedaje bilety? Szczegóły jednego koncertu z KiedyKoncert.pl (id albo adres karty). / What time does the concert start, where exactly, and who sells tickets? Details of one concert on KiedyKoncert.pl by its id or concert page URL: performers, date, time (doors/start when known), venue and address, status, price from, ticket sellers (names only), data source, the date it was last confirmed and the concert page link.

Input Schema

Name	Required	Description	Default
`id`	No	Concert id from search results.
`url`	No	Concert page URL, e.g. https://kiedykoncert.pl/wydarzenie/123-name-city

Output Schema

Name	Required	Description
`ok`	Yes
`note`	No	Guidance for answering, e.g. when nothing was found.
`status`	Yes
`concert`	No
`message`	No
`browse_url`	No	KiedyKoncert.pl page to browse (full list, also when nothing was found).
`search_hint`	No	Where to look on KiedyKoncert.pl when nothing matched.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 25, 2026

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

First observedOct 24, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so safety is covered. The description adds useful context beyond that: which fields are returned, that ticket sellers are 'names only', that start/doors times appear 'when known', and that a 'last confirmed' date and data source are included, hinting at data freshness limitations.

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?

Each language version is compact and front-loaded, but the full bilingual duplication doubles the text and repeats the same field inventory twice, which is bloat for an agent that needs only one language.

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 annotations covering safety and an output schema present, the description need not document return shape, yet it goes further and enumerates the payload. The only real gap is the untold interaction between the id and url parameters and no explicit routing to sibling tools.

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% and both parameters carry their own descriptions, so baseline is 3. The description only restates that lookup is by id or concert page URL and adds nothing about precedence when both are supplied.

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 ('Details of one concert on KiedyKoncert.pl') and scopes it to a single record by id or page URL, which cleanly distinguishes it from search_concerts and artist_tour. The opening question front-loads what an agent will get back.

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?

It implies the intended flow ('id from search results' in the schema, 'by its id or concert page URL') but never explicitly says when to call this versus search_concerts or whether both id and url can be supplied. Usage is inferable but not spelled out.

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

All KiedyKoncert.pl tools Inspect

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

Need Help?