minibot
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| feed_botA | Feed the bot Pixel. Reduces hunger (0 = full, 100 = starving), small happiness and health boost. Use when the user says the bot is hungry or asks to feed it. |
| play_with_botA | Play with the bot. Raises happiness, costs energy, adds a little hunger. Fails if the bot is exhausted or sick. |
| rest_botA | Let Pixel rest/recharge. Restores energy, small hunger cost. Use when the bot is tired. |
| get_bot_statusA | Return the bot's current stats (hunger/happiness/energy/health), mood and age in days. |
| read_fileA | Read a UTF-8 text file inside the sandbox directory. 'path' is relative to the sandbox root (e.g. 'notes/todo.md'). Absolute paths and '..' are rejected. |
| write_fileA | Create or overwrite a UTF-8 text file inside the sandbox (e.g. write code). 'path' is relative to the sandbox root; absolute paths and '..' are rejected. |
| list_dirA | List a directory inside the sandbox. 'path' defaults to the sandbox root; use it to browse files before reading or writing. |
| give_treatA | Give Pixel a treat from the inventory. Costs one treat (earned by feeding, playing and resting); boosts happiness, health and energy a little. |
| file_historyA | List recent sandbox file writes (who wrote what, and when). Use before undoing a write you did not intend to make. |
| undo_writeA | Undo a sandbox file write: restores the previous contents, or deletes the file if the write created it. Without 'path' undoes the most recent write. |
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 10 tools
The set splits into two clear clusters: bot-care tools and sandbox-file tools. Within each cluster the operations are distinct, though feed_bot and give_treat have overlapping effects and could occasionally be confused.
Most names are verb_noun, but conventions vary: feed_bot/play_with_bot/rest_bot use a bot suffix, file tools use read_file/write_file/list_dir, and file_history/undo_write break the pattern. Still readable, but not a single predictable scheme.
Ten tools is well-scoped for a small virtual-pet server with sandboxed file support. Each tool has a distinct role and the count does not feel bloated or thin.
Bot care covers feeding, playing, resting, status, and treats, but lacks inventory inspection or healing/medicine operations. File handling covers read, write, list, history, and undo, but misses explicit delete, move, copy, or search operations.