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. |
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 targets a distinct action: reading status, adopting, and providing care. The only mild overlap is that nest_status reads care receipts while pet_care writes them, but the read/write split keeps them separable.
Names follow a noun_verb-ish pattern, but the prefix is inconsistent: two tools use pet_ while one uses nest_. It is readable but not a clean single convention.
Three tools is thin for a domain that involves pets, pantry, and adoption. It is borderline rather than clearly wrong, but the surface feels under-provisioned.
Adopt, care, and status cover the core loop, but there are notable gaps: no way to list or search adoptable pets, no release/abandon operation, and no pantry management despite pantry being mentioned.