Skip to main content
Glama

Szczegóły koncertu / Concert details

get_concert
Read-onlyIdempotent

Wszystko o jednym koncercie: kiedy, gdzie, kto gra, ile kosztuje bilet i kto go sprzedaje. / One concert from GoGiga: date, time, venue and address, performers, description, price from primary sale and the shops selling tickets. Takes the url (https://gogiga.pl/gig/…) or the slug that search_concerts returned.

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": {
      "concert": "<concert>"
    },
    "name": "get_concert"
  }
}

Input Schema

NameRequiredDescriptionDefault
concertYesThe concert's GoGiga url or slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so safety and repeatability are covered. The description adds useful content scope (primary-sale price plus the shops selling tickets), but says nothing about behavior on an invalid or unknown slug, and nothing about the response shape beyond the field list.

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?

The payload is front-loaded with the essential 'what you get', followed by the accepted input. The Polish/English duplication doubles the length, but each half is tight and free of filler.

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 no output schema, the description compensates by listing the returned fields in detail, which is exactly what an agent needs for a single-record fetch. The only gaps are error behavior for a bad slug and any note on data freshness, both minor for a read-only lookup.

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% and the single parameter is already described, so the baseline is 3. The description goes beyond it by giving the concrete url form (https://gogiga.pl/gig/…) and by telling the agent where the slug originates (search_concerts), which clarifies the accepted value.

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 names a specific verb and resource ('One concert from GoGiga') and enumerates the exact fields returned: date, time, venue and address, performers, description, price from primary sale, and ticket shops. It also distinguishes itself from the search tool by stating that the slug comes from search_concerts, so an agent can tell single-concert lookup apart from search or band-based listing.

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?

Usage is clearly implied: call this after search_concerts, passing either the GoGiga url or the returned slug. No explicit 'when not to use' statement or named comparison to band_concerts/list_festivals is given, which keeps it short of a full 5.

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