The Game Crafter
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TGC_API_BASE | No | API base URL (defaults to https://www.thegamecrafter.com/api) | https://www.thegamecrafter.com/api |
| TGC_PASSWORD | Yes | Your TGC account password | |
| TGC_USERNAME | Yes | Your TGC account username | |
| TGC_API_KEY_ID | Yes | Your TGC API key ID | |
| TGC_UPLOAD_BASE_DIR | No | Restrict file uploads to this directory (defaults to working directory) |
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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_game_catalogA | Browse TGC printable component types (cards, boards, boxes, etc.). No authentication required. |
| authenticateA | Create a TGC session using stored credentials. Must be called before any tool that requires authentication. |
| logoutA | Destroy the current TGC session. |
| get_my_designersA | List designer profiles for the authenticated user. Returns designer ID, name, and user ID. Use the designer_id with get_my_games or create_game. Requires authentication. |
| get_my_gamesA | List all games for a designer with name, ID, and status. Returns paginated results. Requires a designer_id from get_my_designers. Requires authentication. |
| get_game_detailsA | Get full game info including name, description, component list with quantities, file references, and pricing. Use this to review a game before making changes. Requires authentication. |
| create_gameA | Create a new game project under a designer. Requires authentication. |
| add_component_to_gameA | Add a printable component (card deck, board, box, etc.) or stock part to a game. Use a catalog identity (e.g., 'BridgeDeck') for printable components, or a stock part UUID. Requires authentication. |
| upload_fileA | Upload an image file to a TGC folder for use in a game component. This is a heavyweight operation — avoid calling repeatedly in quick succession. Requires authentication. |
| get_component_sizesA | Get pixel dimensions (width, height, bleed, safe zone) and finished inches for TGC component types. Use this to determine correct image sizes before uploading artwork. No authentication required. |
| get_pricing_estimateA | Get per-component cost breakdown and total price for a game at various order quantities. The game must have components added first via add_component_to_game. Requires authentication. |
| update_gameB | Update a game's name, description, or visibility. Requires authentication. |
| get_component_detailsB | Get detailed information about a component type by catalog identity (e.g., 'BridgeDeck') or a game part by UUID. |
| delete_gameA | Permanently delete a game project. This action cannot be undone. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| new_game_setup | Guided workflow for creating a complete TGC game project with components and artwork. |
| estimate_game_cost | Get a cost estimate for a TGC game by reviewing its components and pricing. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| catalog | Full catalog of TGC printable component types (cards, boards, boxes, etc.). |
| component_sizes | Reference sheet of all TGC component pixel dimensions (width, height, bleed, safe zone). |
TDQS
Scored across 14 tools
Each tool has a distinct, well-defined purpose with no overlap. For example, get_component_sizes is purely for dimensions, while get_component_details provides component info, and add_component_to_game is for adding components to games. The descriptions clearly differentiate actions like create_game, update_game, and delete_game.
All tool names follow a consistent verb_noun pattern (e.g., add_component_to_game, create_game, get_game_details). The naming is uniform across all 14 tools, using snake_case throughout with clear action verbs like 'get', 'create', 'update', and 'delete'.
With 14 tools, this server is well-scoped for managing game projects on The Game Crafter platform. It covers authentication, game lifecycle, component management, file uploads, and pricing, which aligns perfectly with the domain's needs without being excessive or insufficient.
The toolset provides complete coverage for the game design and publishing workflow. It includes authentication (authenticate/logout), game CRUD (create_game, get_my_games, update_game, delete_game), component handling (add_component_to_game, get_component_details, get_component_sizes), file management (upload_file), and pricing (get_pricing_estimate), with no apparent gaps for core operations.