Skip to main content
Glama

FoxAPIs data sources

Lichess player

lichess_player
Read-onlyIdempotent

A Lichess player: ratings per variant, game counts, title and account age, by user name. Costs 1 credit a call; an answer with no data is not charged. Needs your FoxAPIs key (free to start).

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": {
      "username": "<username>"
    },
    "name": "lichess_player"
  }
}

Input Schema

NameRequiredDescriptionDefault
usernameYesFor example: "DrNykterstein"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already cover read-only, idempotent and non-destructive traits, but the description adds non-obvious operational context: each call costs 1 credit, empty answers are not charged, and a FoxAPIs key is required. It does not say what happens on an unknown username or whether results are cached, which keeps it below 5.

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 tight sentences: the first front-loads what you get, the second covers cost and authentication. Every clause carries information; nothing is redundant.

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?

With no output schema, the description usefully enumerates the returned fields, and it discloses the cost and auth model for a single-parameter read tool. Minor gaps remain around error behavior for nonexistent users and any rate limits.

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?

There is a single required parameter with 100% schema description coverage, including an example value ("DrNykterstein"). The description's phrase "by user name" adds a little framing but no format rules (case sensitivity, Lichess ID vs display name), so the schema does the real work.

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?

Names a specific resource (a Lichess player) and enumerates the data returned: ratings per variant, game counts, title, account age, keyed by user name. It is clearly distinguishable from chess_player by the explicit Lichess branding, though it never states the contrast outright.

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 only implied: look up a player by name. There is no explicit when-to-use or when-not guidance, and no naming of an alternative such as chess_player for non-Lichess lookups; the only contextual direction is about credits and the API key.

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.

Resources