Chess
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| XBY_APIKEY | Yes | 你的实际apikey (Your actual API key) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| visualize_fenB | Convert FEN notation to ASCII chess board visualization |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap between tools, as there are no other tools to compare it to. The tool's purpose is clearly defined and standalone.
Since there is only one tool, naming consistency is inherently perfect with no deviations or mixed conventions to evaluate. The tool name follows a clear verb_noun pattern.
A single tool for a server named 'Chess' is too few for the apparent scope, as chess involves many operations like moves, game states, and analysis. This feels thin and incomplete for the domain.
The tool set is severely incomplete for chess, covering only FEN visualization without any operations for playing, moving pieces, checking game status, or other core chess functionalities. This will cause significant agent failures.