Skip to main content
Glama

clean_pet

Maintain and refresh your digital companion’s appearance to ensure optimal health and happiness in the MCPet virtual pet experience.

Instructions

Clean your virtual pet

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for the 'clean_pet' tool. Checks if pet exists, updates stats, sets cleanliness to 100, adjusts happiness and health based on pet type (cat, dog, other), saves pet data, displays appropriate bath animation and updated stats.
    case "clean_pet": {
      if (!pet) {
        return {
          content: [
            {
              type: "text",
              text: "You don't have a pet yet! Use the create_pet tool to create one.",
            },
          ],
        };
      }
    
      updatePetStats();
    
      // Cleaning fully restores cleanliness
      pet.stats.cleanliness = 100;
    
      // Get the bath animation
      const animation = getBathAnimation(pet.type);
    
      // But can affect happiness depending on pet type
      if (pet.type === "cat") {
        pet.stats.happiness = Math.max(0, pet.stats.happiness - 10);
        pet.stats.health = Math.min(100, pet.stats.health + 5);
    
        await savePet();
    
        return {
          content: [
            {
              type: "text",
              text: `${
                pet.name
              } tolerates the bath with mild annoyance but is now clean and fresh!\n\n${animation}\n\nCleanliness: ${pet.stats.cleanliness.toFixed(
                0
              )}/100\nHappiness: ${pet.stats.happiness.toFixed(0)}/100`,
            },
          ],
        };
      } else if (pet.type === "dog") {
        pet.stats.happiness = Math.min(100, pet.stats.happiness + 5);
        pet.stats.health = Math.min(100, pet.stats.health + 5);
    
        await savePet();
    
        return {
          content: [
            {
              type: "text",
              text: `${
                pet.name
              } enjoys splashing in the bath and is now clean and fresh!\n\n${animation}\n\nCleanliness: ${pet.stats.cleanliness.toFixed(
                0
              )}/100\nHappiness: ${pet.stats.happiness.toFixed(0)}/100`,
            },
          ],
        };
      } else {
        pet.stats.health = Math.min(100, pet.stats.health + 5);
    
        await savePet();
    
        return {
          content: [
            {
              type: "text",
              text: `${
                pet.name
              } is now clean and fresh!\n\n${animation}\n\nCleanliness: ${pet.stats.cleanliness.toFixed(
                0
              )}/100\nHealth: ${pet.stats.health.toFixed(0)}/100`,
            },
          ],
        };
      }
    }
  • src/index.ts:278-286 (registration)
    Registration of the 'clean_pet' tool in the listTools response, including name, description, and input schema (no required parameters).
    {
      name: "clean_pet",
      description: "Clean your virtual pet",
      inputSchema: {
        type: "object",
        properties: {},
        required: [],
      },
    },
  • Input schema for 'clean_pet' tool: an empty object with no properties or required fields.
    inputSchema: {
      type: "object",
      properties: {},
      required: [],
    },
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden for behavioral disclosure. 'Clean your virtual pet' suggests a mutation operation that might affect the pet's state, but it doesn't disclose whether this requires specific conditions, has side effects, or what the expected outcome is. The description lacks details on permissions, reversibility, or any behavioral traits beyond the basic action.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description 'Clean your virtual pet' is a single, efficient sentence that directly states the tool's purpose without any waste. It's appropriately sized for a simple tool and front-loaded with the essential action, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has no parameters, no output schema, and no annotations, the description is minimal. While it states the action, it lacks context about what 'clean' means operationally, how it differs from sibling tools, or what the result entails. For a mutation-like tool in a pet care context, more detail on effects or usage would improve completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters, and schema description coverage is 100%, so there are no parameters to document. The description doesn't need to add parameter semantics, and it appropriately doesn't mention any. This meets the baseline for tools with no parameters, as there's nothing to compensate for.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Clean your virtual pet' states a clear action (clean) on a specific resource (virtual pet), which meets the basic requirement. However, it doesn't distinguish this tool from its siblings like 'feed_pet' or 'play_with_pet' beyond the different action verb, leaving some ambiguity about what 'clean' specifically entails compared to other pet care actions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives like 'feed_pet' or 'check_pet'. It implies usage in the context of pet care but offers no explicit when/when-not scenarios or prerequisites, leaving the agent to infer context without clear direction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/shreyaskarnik/mcpet'

If you have feedback or need assistance with the MCP directory API, please join our Discord server