Skip to main content
Glama

Find Lichess clubs at a rating

find_lichess_clubs
Read-onlyIdempotent

Up to ten Lichess clubs (teams) where the given rating sits in the middle half of the members' blitz or rapid ratings, largest first, with member counts, medians, how many members were active in the last month, and a Start link for each. Use when a player wants a club at their level.

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": {
      "rating": "<rating>"
    },
    "name": "find_lichess_clubs"
  }
}

Input Schema

NameRequiredDescriptionDefault
ratingYesA Lichess blitz or rapid rating.
open_to_joinNoTrue for clubs anyone can join without approval. Default false.

Output Schema

NameRequiredDescriptionDefault
moreNo
clubsYes
totalYes
ratingYes
open_to_joinNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / open_to_join / description
      Added value: +"True for clubs anyone can join without approval. Default false."
    • addedInput schema / properties / rating / description
      Added value: +"A Lichess blitz or rapid rating."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "clubs": {
      +      "items": {
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "more": {
      +      "type": "string"
      +    },
      +    "open_to_join": {
      +      "type": "boolean"
      +    },
      +    "rating": {
      +      "type": "integer"
      +    },
      +    "total": {
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "rating",
      +    "total",
      +    "clubs"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), and the description adds real behavior beyond that: the selection predicate (rating in the middle half of member blitz/rapid ratings), the ten-result cap, ordering by size, and the returned fields including a Start link. It does not say what happens when no club qualifies, which is the remaining behavioral gap.

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?

Two sentences, front-loaded with the result shape and capped by the usage condition; every clause carries information. The first sentence is dense and stacks several facts (cap, predicate, ordering, return fields), which slightly hurts scannability but wastes no words.

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?

An output schema exists, so return values need not be spelled out, yet the description helpfully previews them anyway. Combined with the selection rule, cap, and ordering, an agent has what it needs to call this correctly; only the empty-result case and the open_to_join toggle are unaddressed.

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%, so both parameters are already documented, and the description's explanation of how the rating is compared (middle half of members' blitz or rapid ratings) adds interpretive value. However, the second parameter, open_to_join, is never mentioned in the description, so it adds nothing for that half of the surface.

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 ('Up to ten Lichess clubs (teams)') and immediately disambiguates the parenthetical 'teams' alongside the selection rule. The scope, cap, and sort order ('largest first') let an agent distinguish it from the ladder-oriented siblings without opening any schema.

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?

"Use when a player wants a club at their level" gives a clear triggering condition tied to the rating-based filter. It stops short of naming alternatives or exclusions (e.g., what to do if the player wants a club open to join), leaving a minor gap.

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.