pet-nest
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PET_NEST_DATA_DIR | No | Private data directory. The web service and MCP process must use the same directory. Defaults to ~/.local/share/cove-pet-nest if unset. |
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 |
|---|---|
| nest_statusC | Read pets, pantry and actual care receipts. Never exposes private relationship text. |
| pet_adoptC | Adopt a pet when the user requests it. Reuse request_id on retries. Some species need image setup. |
| pet_careA | Feed, play or comfort as the AI. Only successful receipts mean care happened; reuse request_id on retries. |
| pet_albumC | Read activated stage portraits and factual life-photo sources. Never queues paid images. |
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 targets a fairly distinct area: pet_album reads images, nest_status reads state/receipts, pet_adopt creates a pet, and pet_care performs care actions. The two read tools (pet_album, nest_status) could be slightly confused at first glance, but their resource boundaries are clear from the descriptions.
Three of four tools follow a consistent pet_<verb/noun> snake_case pattern (pet_album, pet_adopt, pet_care). nest_status is a minor deviation with a different prefix, but it's still readable and predictable.
Four tools is on the lean side but each covers a distinct function (read photos, read status, adopt, care), so the count is reasonable for a focused pet-care domain. It is slightly thin but no tool feels redundant.
The surface covers create (adopt), read (status, album), and an action (care), but there is no update, rename, release/remove-pet, or configuration operation. Core happy-path workflows work, yet lifecycle operations like managing or removing an existing pet are missing.