Skip to main content
Glama

Festiwale i trasy / Festivals and tours

list_festivals
Read-onlyIdempotent

Festiwale muzyczne i trasy koncertowe w Polsce. / Upcoming music festivals and concert tours in Poland on GoGiga, soonest first, 10 a page: dates, towns, number of concerts and the GoGiga page with the programme.

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": "list_festivals"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage of results, 1 by default
typeNoOnly festivals or only tours
queryNoPart of the name, e.g. "Open'er" or "jazz"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds real behavioral value: deterministic ordering (soonest first), page size (10 items), and the shape of each result including the GoGiga programme page. It omits any note on total counts or what happens past page 50.

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 English sentence is well front-loaded and dense with useful facts, but the Polish lead sentence restates the same subject without adding information for a non-Polish reader, so the definition is partly duplicated.

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 a simple read-only listing tool with full schema coverage and no output schema, the description does the heavy lifting by enumerating returned fields and the sort/pagination rules. Only minor gaps remain, such as result-count behavior and ceiling on page depth.

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 all three parameters are already documented in the schema, and the description adds only the '10 a page' detail that contextualizes the page parameter. Nothing further is said about how query matches or how type interacts with the result set.

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?

Names a specific resource (upcoming music festivals and concert tours in Poland) and adds scope details: soonest first, 10 per page, plus the fields returned. It is clear what the tool lists, though it does not explicitly contrast itself with band_concerts or search_concerts.

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: 'Upcoming ... soonest first, 10 a page' signals a browse/discovery tool. There is no explicit when-to-use guidance, no mention of when to prefer search_concerts or band_concerts, and no note on how the type/query filters change the intent.

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