Skip to main content
Glama
Sports Hub MCP Server

Sports Hub MCP Server

by danmorris27

lichess: Get daily puzzle

lichess_get_daily_puzzle
Read-onlyIdempotent

Retrieve the Lichess puzzle of the day, including its source game and solution moves, for daily chess training or analysis.

Instructions

Get the Lichess puzzle of the day, including the source game and the solution moves.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "lichess_get_daily_puzzle"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoKeys to keep (comma-separated).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.1

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so safety and determinism are covered structurally. The description helpfully discloses the return payload (source game plus solution moves), which is useful since no output schema exists, but adds nothing on caching, rate limits, or that the result changes daily.

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 tight sentence that front-loads the resource and immediately lists what is returned. No filler or redundancy.

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, parameterless read tool with annotations covering the safety profile, the description discloses the return contents adequately in the absence of an output schema. A minor gap is the absence of any note on daily rotation or fixed scope, but nothing essential to calling it correctly 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?

Only one optional 'fields' parameter, and the schema description (100% coverage) already documents it. The description adds no further parameter meaning, so the baseline of 3 for fully-covered schema is correct.

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 (Get) and resource (Lichess puzzle of the day), and explicitly names the contents included (source game and solution moves). Easily distinguished from all siblings, none of which concern puzzles.

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

Usage Guidelines3/5

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

The phrase 'puzzle of the day' implies usage context (fetch today's puzzle), but there is no explicit when-to-use guidance, no alternatives, and no mention that it always returns the single current daily puzzle regardless of input.

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