kicksmash

Create a match

create_match

Create a padel match (4 players) or an americano tournament for a person. A tournament may keep fixed pairs (fixedPairs: true): two partners play every round together and the table ranks pairs. Returns the share link for the players and the organizer's private links. Give the person all links; keep personalToken and manageUrl private. Ask before creating; one request, one match.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`tz`	Yes	IANA time zone the players live in, for example Asia/Singapore or Asia/Bangkok.
`cost`	No	What each player pays, as free text: 400 THB, €8, split 4 ways.
`note`	No
`type`	No	A match is exactly four players. A tournament is an americano with 4 to 64 players in fours.	match
`court`	No	Court within the venue, e.g. "3".
`title`	No
`venue`	No	Club or court name. Enables the venue board and the booking link.
`ageMin`	No	An age tag: 35, 45 or 55 means 35+, 45+ or 55+. Omit for any age. Information only; nobody is checked when they join.
`format`	No	Tournaments only. americano: partners rotate, everyone plays everyone. mexicano: courts by standings after round 1. king: winners move up a court, losers down.
`gamesTo`	No	Tournaments only: first to N games (4, 6, 8) instead of points; the table then ranks by matches won.
`capacity`	No	Tournaments only, a multiple of 4. Matches are always 4.
`category`	No	Who the match is for: men, women or mixed. Omit for anyone. Information for the players who find it; nobody is checked when they join.
`levelMax`	No
`levelMin`	No	Level range 0 to 7 (Playtomic-style). Omit both for any level.
`startsAt`	Yes	ISO 8601 date-time. With an offset or Z it is absolute; without one it is read in tz. Example: 2026-09-11T19:00
`whenFull`	No		waitlist
`organizer`	Yes
`bookingUrl`	No	The club's booking page or confirmation link, shown to players.
`fixedPairs`	No	Tournaments only: two partners play every round together, in any format. Pairs sign up together (join_match with partner); a player alone is listed as needing a partner. Americano then rotates the opponents: every pair meets every other pair, and the table ranks pairs.
`venueMapUrl`	No
`organizerPlays`	No	Seat the organizer in the match (default). False when they only organize.
`pointsPerMatch`	No	Tournaments only: fixed points per match (16, 21, 24, 32). Omit for free scoring; mexicano defaults to 24.
`durationMinutes`	No	How long the court is booked: 60, 90 or 120 minutes. Omit for 90 (a match) or 120 (a tournament). The match page, the cards and the calendar invitation show it.
`listOnVenueBoard`	No	Show the match on the public venue board (/v/{venue-slug}). Off by default.
`verifiedLevelsOnly`	No	With a range: only levels confirmed by an organizer, a coach or a club walk in; declared levels inside the range ask to join.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 10, 2026

addedInput schema / properties / ageMin

Added value: +{
+  "anyOf": [
+    {
+      "enum": [
+        35,
+        45,
+        55
+      ],
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "An age tag: 35, 45 or 55 means 35+, 45+ or 55+. Omit for any age. Information only; nobody is checked when they join."
+}

addedInput schema / properties / category

Added value: +{
+  "anyOf": [
+    {
+      "enum": [
+        "men",
+        "women",
+        "mixed"
+      ],
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Who the match is for: men, women or mixed. Omit for anyone. Information for the players who find it; nobody is checked when they join."
+}

addedInput schema / properties / fixedPairs

Added value: +{
+  "default": false,
+  "description": "Tournaments only: two partners play every round together, in any format. Pairs sign up together (join_match with partner); a player alone is listed as needing a partner. Americano then rotates the opponents: every pair meets every other pair, and the table ranks pairs.",
+  "type": "boolean"
+}

Changed1 schema field changedSep 30, 2026

addedInput schema / properties / durationMinutes

Added value: +{
+  "description": "How long the court is booked: 60, 90 or 120 minutes. Omit for 90 (a match) or 120 (a tournament). The match page, the cards and the calendar invitation show it.",
+  "enum": [
+    60,
+    90,
+    120
+  ],
+  "type": "number"
+}

Changed1 schema field changedSep 20, 2026

addedInput schema / properties / gamesTo

Added value: +{
+  "description": "Tournaments only: first to N games (4, 6, 8) instead of points; the table then ranks by matches won.",
+  "maximum": 12,
+  "minimum": 2,
+  "type": "integer"
+}

Changed1 schema field changedSep 9, 2026

addedInput schema / properties / verifiedLevelsOnly

Added value: +{
+  "default": false,
+  "description": "With a range: only levels confirmed by an organizer, a coach or a club walk in; declared levels inside the range ask to join.",
+  "type": "boolean"
+}

First observedSep 7, 2026

TDQS

A3.9/5.0

Behavior4/5

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

With annotations covering only the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), the description adds real behavioral value: it discloses what comes back (share link for players, private organizer links) and a privacy-handling rule (keep personalToken and manageUrl private, share all links with the person). It does not discuss failure modes or duplicate-creation behavior beyond 'one request, one match'.

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?

Four dense sentences with the core purpose front-loaded and the safety directive last. The fixedPairs sentence partly duplicates the schema's own fixedPairs description, which is the only slightly wasteful element.

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 25-parameter creation tool with a nested organizer object and no output schema, the description compensates by describing the return payload (share link plus private organizer links) and the privacy handling. It is complete enough to call correctly, though defaults and edge behavior are left to the schema.

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 76% across 25 parameters, so the schema already carries most semantics. The description restates the match/tournament and fixedPairs meaning that the schema itself explains in more detail, adding little beyond it. Baseline 3 applies.

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 — 'Create a padel match (4 players) or an americano tournament for a person' — and even distinguishes the two creation modes an agent must choose between. It does not name a sibling tool (e.g. join_match) to differentiate against, so it stops short of a 5.

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?

'Ask before creating; one request, one match' gives a concrete pre-call confirmation requirement and a cardinality constraint that prevents bulk creation. However, it offers no guidance on when to create versus when to point the user at join_match or find_matches, and no exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All kicksmash tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Create a match

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources