Skip to main content
Glama

Search sports events / Szukaj meczów i gal

search_events
Read-onlyIdempotent

Search upcoming ticketed sports events in Poland listed on KiedySport.pl: league and national team matches, tournaments, MMA and boxing nights. Filters (all optional, combine freely): discipline, city, club, venue, date_from/date_to or a when shortcut, free-text query. Returns up to 20 events per call (page with offset and next_offset) with date, start time or "wkrótce", venue, city, price from (only when known) and the event page link, plus total_found. Default range: from today on. Example call: {"discipline":"mma-boks"} or {"city":"Katowice","discipline":"mma-boks"}. / Szukaj meczów i gal z biletami: dyscyplina, miasto (także bez polskich znaków), klub, hala, daty, fraza.

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

Input Schema

NameRequiredDescriptionDefault
cityNoPolish city, with or without Polish letters, e.g. "Kraków" or "Krakow". / Miasto.
clubNoClub or team name, short forms accepted (e.g. "Stal Mielec" for "Handball Stal Mielec"). / Klub.
whenNoDate shortcut (Europe/Warsaw); this_weekend = Friday to Sunday of the current week. Overrides date_from/date_to.
limitNoEvents per page (1-20, default 10).
queryNoWords from the event title, team or venue, e.g. "KSW", "Puchar Polski". / Fraza.
venueNoArena, hall or stadium name. / Hala lub stadion.
offsetNoSkip this many matches; use next_offset from the previous page.
date_toNoLast day YYYY-MM-DD (inclusive).
date_fromNoFirst day YYYY-MM-DD (default today).
disciplineNoSport slug (see list_disciplines). Names like "volleyball", "siatkówka", "MMA" are accepted too. / Dyscyplina.

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.1/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world, so the safety profile is covered. The description still adds genuine behavior: a hard cap of 20 events per call, offset/next_offset paging, total_found, default date range, and the caveat that price appears only when known and start time may read 'wkrótce'.

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 English sentence is front-loaded with scope, then filters, then return shape, then examples — a sensible order with no filler. The appended Polish translation restates most of the same content and lengthens the definition without adding new information for an agent.

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 10 optional parameters, an output schema, and full annotation coverage, the definition supplies everything needed to call it: default date range, page size cap, paging fields, and slug guidance. Return-value explanation partially duplicates the output schema, but nothing required for a correct call is missing.

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% and the schema already documents city accents, club short forms, the `when` override of date_from/date_to, and the limit/offset bounds. The description adds little parameter-level meaning beyond the example calls that demonstrate combining discipline and city; baseline 3 applies when the schema does the heavy lifting.

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 verb and resource with scope: 'Search upcoming ticketed sports events in Poland listed on KiedySport.pl', and enumerates the covered event types (league matches, tournaments, MMA/boxing nights). The scope boundary (upcoming, ticketed, Poland, one site) plus the pointer to list_disciplines for slugs lets an agent separate it from get_event and club_schedule.

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?

Says all filters are optional and combine freely, states the default range is 'from today on', and routes the agent to list_disciplines for sport slugs, with two concrete example calls showing filter combination. It does not explicitly say when to prefer get_event or club_schedule instead, so the when-not side is left implicit.

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