Skip to main content
Glama
Sports Hub MCP Server

Sports Hub MCP Server

by danmorris27

lichess: Get top players

lichess_get_top_players
Read-onlyIdempotent

Retrieve the top N Lichess players for a chosen performance variant, such as bullet or blitz, and control how many players and which fields are returned.

Instructions

Get the top N players for a Lichess performance variant (bullet, blitz, rapid, classical, etc.).

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": {
      "perf": "<perf>"
    },
    "name": "lichess_get_top_players"
  }
}

Input Schema

NameRequiredDescriptionDefault
nNoNumber of top players to return (1-200, default 10)
perfYesPerformance variant key
fieldsNoKeys to keep (comma-separated).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=true, so the safety and idempotency profile is covered. The description adds only the ranking/depth semantics ('top N'), and says nothing about caching, rate limits, or roughly what a player entry contains.

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?

A single sentence, front-loaded with verb and resource, with no filler or restated schema detail. Every word earns its place.

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 simple, fully documented read-only endpoint with annotations covering safety, this is nearly complete. The only gap is that with no output schema, the description does not hint at the shape of a returned player entry (name, rating, title), which an agent might otherwise need.

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%: n has a documented range and default, perf has a full enum, and fields explains the comma-separated projection. The description's parenthetical variant list adds mild illustrative value but no format or syntax information 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.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Get) and resource (top N players) scoped to a Lichess performance variant, with examples of the variants inline. The resource is unambiguous and not overlapped by any sibling tool, though it does not explicitly contrast itself with neighboring read tools like lichess_get_user.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no when-to-use or when-not-to-use guidance; it never mentions an alternative tool or the condition (e.g., leaderboards vs. a single user lookup) that should route an agent here. Only the phrase 'top N' implicitly signals a leaderboard-style query.

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

Deploy Server

Other Tools