Skip to main content
Glama

kicksmash

by sh.kicksma
OverviewDiscussionsAdmin

Create a match

create_match

Create a padel match (4 players) or an americano tournament for a person. 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
NameRequiredDescriptionDefault
tzYesIANA time zone the players live in, for example Asia/Singapore or Asia/Bangkok.
costNoWhat each player pays, as free text: 400 THB, €8, split 4 ways.
noteNo
typeNoA match is exactly four players. A tournament is an americano with 4 to 64 players in fours.match
courtNoCourt within the venue, e.g. "3".
titleNo
venueNoClub or court name. Enables the venue board and the booking link.
formatNoTournaments only. americano: partners rotate, everyone plays everyone. mexicano: courts by standings after round 1. king: winners move up a court, losers down.
gamesToNoTournaments only: first to N games (4, 6, 8) instead of points; the table then ranks by matches won.
capacityNoTournaments only, a multiple of 4. Matches are always 4.
levelMaxNo
levelMinNoLevel range 0 to 7 (Playtomic-style). Omit both for any level.
startsAtYesISO 8601 date-time. With an offset or Z it is absolute; without one it is read in tz. Example: 2026-09-11T19:00
whenFullNowaitlist
organizerYes
bookingUrlNoThe club's booking page or confirmation link, shown to players.
venueMapUrlNo
organizerPlaysNoSeat the organizer in the match (default). False when they only organize.
pointsPerMatchNoTournaments only: fixed points per match (16, 21, 24, 32). Omit for free scoring; mexicano defaults to 24.
listOnVenueBoardNoShow the match on the public venue board (/v/{venue-slug}). Off by default.
verifiedLevelsOnlyNoWith 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.

  1. Changed1 schema field changed
    • 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"
+}
  2. Changed1 schema field changed
    • 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"
+}
  3. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations are minimal (all hints false), so the description carries the behavioral burden. It discloses that the tool returns a share link and private links, and warns about handling personalToken and manageUrl. 'One request, one match' adds a constraint. No contradiction with annotations; it adds useful behavior beyond the structured hints.

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?

Three short sentences, front-loaded with the operation and resource, followed by output and operational guidance. Every sentence earns its place; no redundant or vague wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 appropriately states the returns (share link, private links). However, for a 21-parameter tool with nested objects, it omits high-level workflow guidance—for example, that the agent must collect required startsAt, tz, and organizer details—and does not clarify the manual or link-based joining flow beyond giving links.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 71%, so the baseline is not automatically high. The description adds only generic hints ('4 players', 'americano') that map to the type/format fields but does not explain key parameters like cost, level, venue, or startsAt semantics. Despite the rich schema, the description contributes little extra meaning for parameters.

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 clearly states a specific verb ('Create') and resource ('padel match (4 players)' or 'americano tournament') and indicates the beneficiary ('for a person'). It distinguishes itself from siblings like book_lesson and join_match by naming the creation targets, though it does not explicitly contrast with those alternatives.

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?

The description provides operational context: ask before creating, one request one match, give all links, and keep personalToken/manageUrl private. However, it does not explicitly state when to prefer this tool over alternatives such as join_match or book_lesson; the context is clear but no exclusions or alternative routing are given.

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

All kicksmash toolsInspect
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.

Resources