Skip to main content
Glama
Sports Hub MCP Server

Sports Hub MCP Server

lichess: Get tournaments

lichess_get_tournaments
Read-onlyIdempotent

Fetch current Lichess Arena tournaments (created, started, recently finished) to track chess events and results.

Instructions

Get current Lichess Arena tournaments (created, started, and recently finished).

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_tournaments"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoKeys to keep (comma-separated).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.4.1
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • addedInput schema / properties / fields
      Added value: +{
      +  "description": "Keys to keep (comma-separated).",
      +  "type": "string"
      +}
  2. First observedv1.2.0

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 the safety profile is covered. The description's one real addition is defining the temporal window of 'current' (created/started/recently finished), which is useful, but it says nothing about result volume, ordering, pagination, or whether a token is needed.

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?

One sentence, front-loaded with verb and resource, with the scope qualifier in parentheses. Nothing superfluous and nothing padded.

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 read-only list endpoint with no output schema and one fully documented parameter, the description covers what is returned closely enough for correct invocation. The only gaps are return volume/ordering and auth expectations, which are minor for this shape of tool.

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% and the single optional 'fields' key is documented there, so baseline 3 applies. The description adds no projection/syntax detail (e.g., how 'fields' interacts with the returned tournament objects) beyond what the schema already gives.

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+resource ('Get current Lichess Arena tournaments') and immediately disambiguates the scope of 'current' as created, started, and recently finished. No sibling tool in the list returns Lichess tournaments, so a single clear sentence is enough to route the agent correctly.

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?

Usage is implied by the description: call it to fetch the currently relevant tournament list. There is no statement of when to prefer it over another tool or of any prerequisite, but with no competing Lichess tournament sibling and zero required parameters, no strong exclusion guidance is needed.

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