m5-petit-desire
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CHARACTER_ID | No | Character ID used to determine paths for desire_config.json and desires.json | default |
| DESIRES_PATH | No | Output path for desires.json | $PETIT_DATA_DIR/characters/<character_id>/data/desires.json |
| COMPANION_NAME | No | Name of the companion, used for automatic keyword generation for miss_companion desire | あなた |
| MEMORY_DB_PATH | No | Path to the SQLite database used by m5-petit-memory | ~/.claude/memories/<character_id>/memory.db |
| PETIT_DATA_DIR | No | Data directory shared with m5-petit-app | ~/petit_data |
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": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_desiresA | Get current desire levels. Act immediately on any desire with level >= 0.7. |
| satisfy_desireA | Satisfy a desire after taking an action. Pass the desire_name you just acted on. The level drops by 0.4. Call again if still high. |
| boost_desireA | Boost a desire level due to novelty/surprise (dopamine/prediction error). Call when you feel surprised or encounter unexpected info. Simulates dopamine response to novelty. |
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 3 tools
Each tool has a distinctly different purpose: get_desires reads current levels, satisfy_desire reduces a desire, and boost_desire increases a desire. There is no overlap or confusion between them.
All tool names follow a consistent verb_noun pattern: get_desires, satisfy_desire, boost_desire. The naming is uniform and predictable.
Three tools is an appropriate scope for a desire management system, covering the essential operations (read, decrease, increase) without unnecessary bloat.
The tool set provides complete coverage of the domain: it allows checking desire levels, satisfying desires to lower them, and boosting desires to raise them. There are no obvious missing operations for the stated purpose.