Skip to main content
Glama

Koncerty zespołu / A band's upcoming concerts

band_concerts
Read-onlyIdempotent

Gdzie i kiedy zagra mój zespół? / Find a band or artist on GoGiga (Polish and foreign artists playing in Poland) and list its upcoming concerts in Poland, with its GoGiga page. Up to 3 bands matching the name, 10 concerts each.

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": {
      "band": "<band>"
    },
    "name": "band_concerts"
  }
}

Input Schema

NameRequiredDescriptionDefault
bandYesBand or artist name, e.g. "Dżem" or "Metallica"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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 and closed-world, so the safety profile is covered. The description adds genuinely useful behavior beyond them: matching is by name with a cap of 3 bands and 10 concerts each, and results include the band's GoGiga page — truncation behavior an agent would otherwise not know.

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?

Two compact sentences; the scope and the result limits are front-loaded and every clause carries information. Minor waste in repeating the bilingual Polish question already present in the title, which costs a little.

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 one-parameter, annotation-rich lookup with no output schema, the description covers domain scope, matching behavior, result caps and the inclusion of the GoGiga page. Only edge behavior (no match found) and result shape details are left unspecified, which is acceptable here.

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?

Schema coverage is 100% with an example value for the single 'band' parameter, so the baseline is a 3. The description adds meaning beyond the schema by indicating that matching is partial/name-based (up to 3 bands may match) and that both Polish and foreign artists playing in Poland are covered.

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 concrete verb and resource: find a band/artist on GoGiga and list its upcoming concerts in Poland, returning its GoGiga page. It also scopes the domain (Polish and foreign artists playing in Poland), which differentiates it in substance from search_concerts, but it never names a sibling or states the routing rule explicitly.

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 by the framing question 'Gdzie i kiedy zagra mój zespół?' and by the band-name lookup, which tells the agent this is for band-centric concert listings. There is no explicit when-not guidance and no mention of the sibling tools (search_concerts, get_concert, list_festivals) that an agent might otherwise pick.

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