KiedyKoncert.pl

Gatunki muzyczne / Music genres

list_genres

Read-onlyIdempotent

Jakie gatunki muzyczne można wybrać i ile jest koncertów każdego? / Which music genres are there and how many upcoming concerts each has? Genres used by KiedyKoncert.pl (slug, Polish name, number of upcoming concerts) for the genre filter of search_concerts.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`ok`	Yes
`note`	No	Guidance for answering, e.g. when nothing was found.
`genres`	No
`status`	Yes
`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

A4.5/5.0

Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive, closed-world operation. The description adds useful behavioral context: the genres come from KiedyKoncert.pl and the concert counts are specifically for upcoming concerts, which goes beyond what the annotations declare.

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?

The description is front-loaded with the core question and answer, then adds the returned fields and integration context. Despite being bilingual, it remains short and each sentence contributes useful information.

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 parameterless read-only listing tool with rich annotations and an output schema, the description provides everything needed: what the tool returns, where the genre data comes from, and how it relates to search_concerts. No critical context is missing.

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?

The tool has zero parameters, so there is no parameter semantics burden. The schema is empty and the description does not need to explain any inputs; baseline 4 is appropriate.

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?

The description clearly states that the tool lists music genres with the number of upcoming concerts for each. It also specifies the returned fields (slug, Polish name, concert count) and explicitly ties the resource to the genre filter of search_concerts, distinguishing it from the sibling tools.

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?

The phrase 'for the genre filter of search_concerts' gives clear context that this tool should be used when genre filtering is needed. However, it does not explicitly state when not to use it or name a direct alternative, so it falls short of a full when/when-not guideline.

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?