Skip to main content
Glama

Convert a Lichess or chess.com rating

estimate_rating
Read-onlyIdempotent

Converts one rating between Lichess and chess.com for a time control, from people who play on both sites. Give lichess or chesscom (exactly one) and time_control. Returns the estimate on the other site and the range most people with that rating fall in.

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": {
      "time_control": "<time_control>"
    },
    "name": "estimate_rating"
  }
}

Input Schema

NameRequiredDescriptionDefault
lichessNoA Lichess rating to convert to chess.com.
chesscomNoA chess.com rating to convert to Lichess.
time_controlYesTime control. Each site and time control is its own rating pool.

Output Schema

NameRequiredDescriptionDefault
toYes
fromYes
noteNo
sourceYes
time_controlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / chesscom / description
      Added value: +"A chess.com rating to convert to Lichess."
    • addedInput schema / properties / lichess / description
      Added value: +"A Lichess rating to convert to chess.com."
    • addedInput schema / properties / time_control / description
      Added value: +"Time control. Each site and time control is its own rating pool."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "from": {
      +      "type": "object"
      +    },
      +    "note": {
      +      "type": "string"
      +    },
      +    "source": {
      +      "type": "string"
      +    },
      +    "time_control": {
      +      "type": "string"
      +    },
      +    "to": {
      +      "type": "object"
      +    }
      +  },
      +  "required": [
      +    "from",
      +    "to",
      +    "source"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.5/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, non-destructive, closed-world), so the description's extra value is the methodology note that the estimate comes from players active on both sites, plus what the response includes (an estimate and a typical range). That is real context beyond the annotations, though precision or caveats about the estimate are not discussed.

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?

Three short sentences: purpose first, then the input rule, then what comes back. No filler and nothing repeated from the schema or title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter, read-only conversion tool with an output schema and full annotation coverage, the description supplies the input contract, the derivation method, and the shape of the result. Nothing an agent needs in order to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline would be 3, but the description adds meaning the schema does not encode: exactly one of lichess or chesscom must be supplied. That mutual-exclusion rule is otherwise only implied by the required list, making the description genuinely useful here.

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: converting a rating between Lichess and chess.com, scoped by time control. The scope sentence ('from people who play on both sites') makes clear this is an estimate derived from dual-site players, distinguishing it from a raw lookup or percentile tool.

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?

Gives a clear invocation rule: 'Give lichess or chesscom (exactly one) and time_control', which resolves the mutual exclusion an agent could otherwise get wrong. It does not name exclusions or point at alternatives such as rating_percentile, so it stops short of a 5.

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.