Skip to main content
Glama

Get a public ladder

get_public_ladder
Read-onlyIdempotent

Standings of one public ladder, by id or ladder link: each named player's Lichess and chess.com rating, change and games in one time control, sorted as on the ladder page, plus this week's awards and recent results. Comes in pages; use offset for the next page. Private and link-only ladders are never returned.

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": {
      "id": "<id>"
    },
    "name": "get_public_ladder"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe ladder id, the part after /l/ in its link (for example demo-club), or the whole link.
limitNoPlayers per page. Default 20.
offsetNoPlayers to skip, for the next page. Default 0.
periodNoDays to measure change over: 7 (default) or 30, or season for a ladder with seasons.
time_controlNoTime control to rank by. Default: the one most of the club plays.
results_limitNoHow many recent weekly awards and challenge results to include. Default 5.

Output Schema

NameRequiredDescriptionDefault
shownYes
ladderYes
periodNo
sorted_byNo
standingsYes
this_weekNo
next_offsetNo
time_controlNo
recent_awardsNo
time_controlsNo
challenge_resultsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changed
    • addedInput schema / properties / id / description
      Added value: +"The ladder id, the part after /l/ in its link (for example demo-club), or the whole link."
    • changedInput schema / properties / id / maxLength
      Previous value: -60New value: +80
    • changedInput schema / properties / id / minLength
      Previous value: -1New value: +4
    • changedInput schema / properties / id / pattern
      Previous value: -"^[a-z0-9-]+$"New value: +"^(https://(www\\.)?chessclubladder\\.com/l/)?[a-z0-9-]{4,40}/?$"
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Players per page. Default 20.",
      +  "maximum": 20,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "description": "Players to skip, for the next page. Default 0.",
      +  "maximum": 2000,
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • addedInput schema / properties / period / description
      Added value: +"Days to measure change over: 7 (default) or 30, or season for a ladder with seasons."
    • changedInput schema / properties / period / enum
      Previous value: -[
      -  "7",
      -  "30"
      -]New value: +[
      +  "7",
      +  "30",
      +  "season"
      +]
    • changedInput schema / properties / period / maxLength
      Previous value: -2New value: +6
    • addedInput schema / properties / results_limit
      Added value: +{
      +  "description": "How many recent weekly awards and challenge results to include. Default 5.",
      +  "maximum": 10,
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • addedInput schema / properties / time_control
      Added value: +{
      +  "description": "Time control to rank by. Default: the one most of the club plays.",
      +  "enum": [
      +    "bullet",
      +    "blitz",
      +    "rapid",
      +    "classical",
      +    "daily"
      +  ],
      +  "maxLength": 9,
      +  "type": "string"
      +}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "challenge_results": {
      +      "anyOf": [
      +        {
      +          "type": "array"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "ladder": {
      +      "type": "object"
      +    },
      +    "next_offset": {
      +      "anyOf": [
      +        {
      +          "type": "integer"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "period": {
      +      "type": "object"
      +    },
      +    "recent_awards": {
      +      "items": {
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "shown": {
      +      "type": "object"
      +    },
      +    "sorted_by": {
      +      "type": "string"
      +    },
      +    "standings": {
      +      "items": {
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "this_week": {
      +      "type": "object"
      +    },
      +    "time_control": {
      +      "type": "string"
      +    },
      +    "time_controls": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "ladder",
      +    "standings",
      +    "shown"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world, and non-destructive behavior. The description adds useful operational detail beyond those annotations: pagination, sort order, included sections, and the visibility rule excluding private/link-only ladders.

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 compact sentences front-load the returned content, then add pagination and visibility constraints. Every clause carries operational meaning, with no filler or repetition.

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 six-parameter read tool with an output schema and full annotation coverage, the description supplies the essential retrieval, pagination, and visibility context. It leaves the choice among sibling lookup tools implicit, but the core completeness is high.

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 all six parameters are already documented in the schema. The description confirms id/link input, offset pagination, and time-control scoping, but adds little syntax or meaning beyond the schema's own parameter descriptions.

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 precisely what the tool returns: standings for one public ladder identified by id or link, including ratings, change, games, awards, and recent results. The phrase 'one public ladder' distinguishes it from list-style siblings, and the visibility boundary is 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?

Explains pagination via offset and states that private and link-only ladders are never returned, giving clear usage context. It does not explicitly compare against alternatives such as list_public_ladders or explain how to obtain a ladder id, so it stops short of full routing guidance.

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.