Skip to main content
Glama

kicksmash

by sh.kicksma

Join a match

join_match

Put a person into a match by first name (or by their personal token from an earlier call). Handles waitlists and level ranges; when the level is outside the range, the organizer is asked to approve.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYesThe 4-character match code from the link, e.g. kicksma.sh/AB12 → AB12.
nameNoRequired unless token is given.
emailNoOptional. Sends a calendar invite that updates itself.
levelNoNeeded once when the match has a level range and the player has no level yet.
tokenNoPersonal token of an existing player.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only mark this as non-read-only, so the description adds value by disclosing waitlist handling, level-range behavior, and organizer approval when the level is out of range. It does not cover every side effect, but the key non-obvious behaviors are surfaced.

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?

Two sentences front-load the main action and then add the two important edge behaviors (waitlists and approval). There is no redundant or filler content.

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?

Together with a fully descriptive schema, the definition gives an agent the essential call context: required code, person identification by name or token, optional email, and level behavior with approval. It lacks an explicit note about success/response, but no output schema exists and the invocation path is otherwise well specified.

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 explains code, the name/token condition, optional email, and level. The description reinforces the name-vs-token choice and level-range context but does not add meaning beyond the schema, so the baseline 3 applies.

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?

The description states a specific action ('Put a person into a match'), identifies the resource (a match by code, person by name/token), and distinguishes it from siblings like create_match and find_matches. The waitlist/level-range behavior adds further specificity.

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?

It clearly indicates this is for adding an existing person to an existing match using a match code, with token as the alternative for known players. It does not explicitly contrast with siblings such as create_match, but the intended context is clear.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation5/5

Each tool targets a clearly distinct resource or action: about/API key, match creation, club searching, match searching, schedule generation, group retrieval, match retrieval, and joining. Even similar tools like find_matches and get_match are separated by clear inputs and purposes.

Naming Consistency4/5

Nearly all tools follow the verb_noun pattern: create_match, find_clubs, find_matches, generate_schedule, get_group, get_match, join_match, create_api_key. The only deviation is about_kicksmash, which uses a preposition-style prefix instead of a verb.

Tool Count5/5

Nine tools is well-scoped for a padel-focused assistant. Each tool serves a distinct user need without redundancy or bloat.

Completeness4/5

The core workflows—discovering clubs/matches, creating matches, joining matches, retrieving match/group info, and generating schedules—are well covered. Update/cancel/leave operations are absent, but the organizer manageUrl suggests those happen outside the MCP surface, so this is a minor gap rather than a dead end.

Resources