Skip to main content
Glama

Start a ladder for a club

start_club_ladder
Read-onlyIdempotent

Use when someone wants a rating ladder for their own chess club, class or group. Give the club's Lichess team or chess.com club as a link, an id or a name. Returns the club as found, a Start page link with that club filled in, what the free plan and the Club pass include, and the Discord app link when the club uses Discord. The organizer creates the ladder in the browser from that link; this tool creates nothing.

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

Input Schema

NameRequiredDescriptionDefault
clubYesA Lichess team link (lichess.org/team/...), a chess.com club link (chess.com/club/...), a team id or club slug, or the club's name.
siteNoWhich site the club is on. Needed only when club is a bare id; narrows a name search.
uses_discordNoTrue when the club has a Discord server, false when it has none. Leave out when not known.

Output Schema

NameRequiredDescriptionDefault
clubNo
foundYes
plansYes
stepsYes
reasonNo
discordNo
start_urlYes
candidatesNo
creates_nothingNo
existing_public_laddersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedOutput schema / properties / query
      Removed value: -{
      -  "type": "string"
      -}
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, but the description adds the crucial non-obvious behavior: the tool provisions nothing and the organizer must complete ladder creation in the browser from the returned link. It also enumerates what comes back (club as found, Start page link, plan contents, Discord link), so the agent knows exactly what the call yields.

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 tightly packed sentences plus a clarifying clause: trigger first, input formats second, return payload third, and the 'creates nothing' caveat last where it lands with maximum effect. No filler or repetition.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only, three-parameter tool with full schema coverage, rich annotations and an output schema, the description covers everything an agent needs: when to call it, what to pass, what comes back, and the fact that a human must finish the job in the browser. Nothing material 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 coverage is 100% and each of the three parameters is documented in the schema, so baseline is 3. The description restates the accepted formats for 'club' (Lichess team or chess.com link, id, or name) but adds no new semantics for 'site' or 'uses_discord' beyond what the schema already explains.

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 ('rating ladder for their own chess club, class or group') and immediately resolves the tension with the tool name by declaring 'this tool creates nothing' — it returns a Start page link. An agent can distinguish it from list_public_ladders/get_public_ladder because the 'their own club' scoping and the hand-off framing are explicit.

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?

Opens with a clear trigger condition ('Use when someone wants a rating ladder for their own chess club...') and implicitly contrasts with browsing public ladders through the private-club framing. No sibling is named as an alternative and there are no explicit when-not-to-use rules, so it stops short of a 5.

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.