MCPet
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_petC | Create a new virtual pet |
| check_petC | Check on your virtual pet's status |
| feed_petC | Feed your virtual pet |
| play_with_petC | Play with your virtual pet |
| clean_petC | Clean your virtual pet |
| put_to_bedB | Put your virtual pet to sleep to restore energy |
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 6 tools
Every tool has a clearly distinct purpose with no ambiguity: create_pet initializes a new pet, while check_pet monitors status, and feed_pet, clean_pet, play_with_pet, and put_to_bed each handle specific care actions. The descriptions reinforce unique functions, making misselection unlikely.
All tools follow a consistent verb_noun pattern with snake_case, such as check_pet, feed_pet, and play_with_pet. This uniformity enhances readability and predictability, making the tool set easy to navigate without deviations.
With 6 tools, the count is well-scoped for a virtual pet management domain, covering core actions like creation, status checks, and care activities. Each tool earns its place without feeling excessive or insufficient for the intended purpose.
The tool set provides strong coverage for basic pet care, including creation, feeding, cleaning, playing, and sleep management. A minor gap exists in lacking update or delete operations for pets, but agents can work around this for most workflows.