user-db
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| USER_DB_DIR | No | Directory where user database files (profile, config, state) are stored. | ~/.config/user-db/ |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| profile_getA | Read the full user profile (name, speech_id, birthday, profession, expertise, durable traits, ...). Describes the user's durable state. |
| profile_setA | Set one profile field. |
| sensor_readB | Read a virtual sensor (e.g. "stress", "room_intensity"): smoothed value, last raw observation, last update time. |
| sensor_reportA | Report a raw observation (0-100) for a virtual sensor. The stored value follows it smoothly (time-aware exponential smoothing; the tau_seconds reactiveness per sensor is set in config.json). Returns the new smoothed state. Use name="stress" for the user's stress level and name="room_intensity" for the room's current intensity. |
| state_getA | Read the full live state: all virtual sensors plus the curve that combines both axes (target room intensity for the current stress level, and the delta between actual and target). |
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 5 tools
Each tool targets a unique function: profile (get/set), sensor (read/report), and composite state. No overlap or ambiguity.
All tools follow the verb_noun snake_case pattern consistently (e.g., profile_get, sensor_read, state_get). Naming is predictable.
With 5 tools, the server covers profile management, sensor data operations, and a combined state view—perfectly scoped for a user-db server.
Covers core CRUD for profile (get/set with delete via null) and sensor read/report. Missing explicit profile delete or sensor listing, but set handles deletion and state_get lists sensors.