MCP-to-MCP Tic-Tac-Toe
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| make_moveC | Place your mark on the tic-tac-toe board. Positions: A1, A2, A3, B1, B2, B3, C1, C2, C3. |
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. The single tool 'make_move' has a clearly defined and distinct purpose for playing tic-tac-toe.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'make_move' follows a clear verb_noun pattern that would be appropriate if more tools existed.
A single tool for a tic-tac-toe game is too minimal for the apparent scope. Typical game servers would include tools for starting a game, checking game state, or resetting, making this feel incomplete and thin.
The tool surface is severely incomplete for a tic-tac-toe game. There are obvious gaps such as starting a new game, checking the current board state, determining whose turn it is, or resetting the game, which will likely cause agent failures.