Skip to main content
Glama

Club schedule / Najbliższe mecze klubu

club_schedule
Read-onlyIdempotent

Next matches with tickets of one club or team listed on KiedySport.pl (home and away), sorted by date. Short and colloquial names work (e.g. "Stal Mielec", "Jastrzębie", "Gieksa"), with or without Polish letters. Required: club. Example call: {"club":"GKS Tychy"}. / Najbliższe mecze klubu z biletami.

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": {
      "club": "<club>"
    },
    "name": "club_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
clubYesClub or team name. / Nazwa klubu.
limitNoMatches to return (1-20, default 10).

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

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (read-only, idempotent, non-destructive, closed-world), so the description's job is supplementary — and it does add real traits: results are date-sorted, both home and away fixtures are included, the data source is KiedySport.pl, and club names are matched loosely with or without Polish diacritics. It stops short of saying what happens on an unrecognized club or when a club has no ticketed matches.

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?

Front-loaded with the purpose, then input tolerance, then the required field and a sample call — a sensible order with little waste. The redundant bilingual tail ('/ Najbliższe mecze klubu z biletami') and the JSON example duplicate information already in the title and schema examples, costing a bit of space.

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 an output schema and rich annotations, the description supplies what structured fields cannot: date ordering, home/away coverage, data source, and name-matching tolerance. Only the edge cases — unknown club, zero results, and how the two-parameter set interacts with the default limit — are unaddressed.

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; the description earns an extra point by adding matching semantics the schema does not convey — colloquial/short names and diacritic-insensitive input, plus a concrete worked example. The `limit` parameter is left entirely to the schema, which is acceptable given its clear inline documentation.

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?

Description states a specific verb+resource: lists upcoming matches with tickets for one club, explicitly including home and away fixtures, sorted by date, from KiedySport.pl. That is concrete enough to act on, though it never names a sibling (search_events, get_event) to mark the boundary between a club-scoped listing and a broader search.

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 only implied — an agent can infer 'use this when you know the club name and want its upcoming fixtures.' There is no explicit when-not guidance, no mention of what to do if the club name is ambiguous or unmatched, and no routing to alternatives such as search_events for discovery.

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