Skip to main content
Glama

Event details / Szczegóły wydarzenia

get_event
Read-onlyIdempotent

One sports event on KiedySport.pl by its id (slug from search_events or club_schedule) or page URL: date, weekday, start time or "wkrótce" (not announced yet), venue with address, teams, price from (only when the seller published it), official ticket seller links and the event page link. Example call: {"id":"avia-sedziszow-malopolski-stal-nysa-sedziszow-malopolski-2026-11-22"}. / Szczegóły jednego wydarzenia: termin, godzina, hala z adresem, cena od, link do sprzedawcy.

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

Input Schema

NameRequiredDescriptionDefault
idNoEvent id (slug) from search_events.
urlNoEvent page URL, format https://kiedysport.pl/wydarzenie/<id>/ (also /en/event/<id>/).

Output Schema

NameRequiredDescriptionDefault
okYestrue = the tool ran (also when nothing was found; read status).
statusYes
messageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the description's job is to add data-quality context, which it does: start time may read "wkrótce" when not announced, and price is present only when the seller published it. The one-of relation between id and url is also surfaced, though nothing is said about error behaviour for an unknown id.

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?

Front-loaded with the resource and key type, then the returned fields, then an example call; nothing is wasted. The Polish sentence is a deliberate bilingual mirror of the first sentence rather than padding, and the one long list is easy to skim.

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 two-parameter read-only detail tool with an output schema and full annotations, nothing an agent needs to call it correctly is missing: key source, alternative key, format, example, and the two caveats on returned data are all present.

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%, so the baseline is 3, but the description adds real meaning beyond the schema by framing the two optional parameters as alternatives ('by its id ... or page URL') — a one-of relationship the schema does not state, since required is empty. It also supplies a worked example call and labels the id as a slug.

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?

States a specific resource ('One sports event on KiedySport.pl') with a specific retrieval key (id/slug or page URL) and enumerates exactly what comes back: date, weekday, start time, venue with address, teams, price from, seller links. It explicitly attributes the id to search_events or club_schedule, which separates it cleanly from those siblings.

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?

Clear context: use this as the detail lookup keyed on an id obtained from search_events or club_schedule, or on a page URL directly. There are no explicit exclusions (e.g., what to do for a list or a multi-event query), but for a read-only detail endpoint the routing guidance is sufficient in practice.

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