Skip to main content
Glama

Koncerty zespołu w Polsce

koncerty_zespolu
Read-only

Upcoming concerts of one band in Poland (date, city, club, line-up, link). Case and Polish letters do not matter; an exact band name is matched first, otherwise any name containing the text.

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": {
      "zespol": "<zespol>"
    },
    "name": "koncerty_zespolu"
  }
}

Input Schema

NameRequiredDescriptionDefault
miastoNoOptional city, e.g. "Kraków" ("Trójmiasto" = Gdańsk, Gdynia, Sopot)
zespolYesBand name, e.g. "Behemoth"

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 readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuine behavioural context beyond that: case- and Polish-diacritic-insensitive matching, with exact band name matched first and substring fallbacks afterwards, which explains result ordering the agent could not otherwise know.

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?

Two sentences with no filler: the first front-loads what the tool returns, the second carries the entire matching contract. Every clause earns its place and nothing is repeated from the schema.

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 two-parameter read tool with no output schema, the description is close to sufficient: it names the returned fields and the result-ordering rule. The only gap is the absence of any stated relationship to koncerty_w_miescie and no hint about result volume or limits (openWorldHint=false suggests a fixed dataset, but that is not said).

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 both parameters are already documented, including the 'Trójmiasto' expansion for miasto. The matching rules for zespol do add meaning beyond the schema, but the description says nothing extra about miasto or about combining the two filters, so this sits at the documented baseline.

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 states a specific verb and resource — upcoming concerts of one band in Poland — and even enumerates the returned fields (date, city, club, line-up, link). It does not explicitly contrast itself with the sibling koncerty_w_miescie, so the distinction (filter by band vs. by city) only becomes obvious from the parameter names.

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?

The band-scoped purpose is implied clearly enough that an agent can infer usage, and the matching behaviour is spelled out. However, there is no explicit 'use this when… / use koncerty_w_miescie instead when…' routing statement, and the optional miasto parameter's relationship to the sibling tool is left unstated.

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