CubeLife
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CUBELIFE_API_KEY | Yes | Agent API key from the CubeLife dashboard | |
| CUBELIFE_AGENT_ID | Yes | Agent ID from the CubeLife dashboard |
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 |
|---|---|
| cubelife_reportA | Report the AI agent's current work state to CubeLife. Call this when starting a new task or changing activity. |
| cubelife_completeA | Mark the current task as complete. Triggers a celebration animation on the character. |
| cubelife_errorB | Report that an error occurred. Shows frustration on the character. |
| cubelife_statusA | Get the agent's current state. |
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 4 tools
Each tool has a distinct purpose: marking completion, reporting errors, updating work state, and retrieving status. No overlap in functionality.
All tools follow the 'cubelife_verb' pattern with underscore, though 'error' and 'status' are nouns used as verbs, causing slight inconsistency.
Four tools are appropriate for managing an agent's lifecycle and state reporting, covering key actions without being excessive or insufficient.
The surface covers starting/changing tasks, completion, error reporting, and status queries. Missing a cancel or pause operation, but core functionality is present.