Skip to main content
Glama

put_to_bed

Restore your virtual pet's energy by putting it to sleep. This tool helps ensure your digital companion stays healthy and thrives in the MCPet server's nurturing environment.

Instructions

Put your virtual pet to sleep to restore energy

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler logic for the 'put_to_bed' tool. It checks if a pet exists, updates stats, fully restores energy to 100, increases health by up to 10, saves the pet data, retrieves a sleeping animation, and returns a response with the animation and updated stats.
    case "put_to_bed": {
      if (!pet) {
        return {
          content: [
            {
              type: "text",
              text: "You don't have a pet yet! Use the create_pet tool to create one.",
            },
          ],
        };
      }
    
      updatePetStats();
    
      // Sleeping fully restores energy and improves health
      pet.stats.energy = 100;
      pet.stats.health = Math.min(100, pet.stats.health + 10);
    
      await savePet();
    
      // Get the sleeping animation
      const animation = getSleepingAnimation(pet.type);
    
      return {
        content: [
          {
            type: "text",
            text: `${
              pet.name
            } gets a good night's sleep and wakes up refreshed!\n\n${animation}\n\nEnergy: ${pet.stats.energy.toFixed(
              0
            )}/100\nHealth: ${pet.stats.health.toFixed(0)}/100`,
          },
        ],
      };
    }
  • src/index.ts:287-295 (registration)
    Registration of the 'put_to_bed' tool in the ListToolsRequestSchema handler, including the tool name, description, and input schema (no required parameters).
    {
      name: "put_to_bed",
      description: "Put your virtual pet to sleep to restore energy",
      inputSchema: {
        type: "object",
        properties: {},
        required: [],
      },
    },
  • Input schema for the 'put_to_bed' tool, which requires no parameters.
    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 the full burden of behavioral disclosure. It states the action ('put to sleep') and outcome ('restore energy'), but doesn't describe side effects (e.g., does this make the pet unavailable for other actions?), time requirements, or success conditions. For a mutation tool with zero annotation coverage, this leaves significant behavioral gaps.

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 is a single, efficient sentence that front-loads the key action and purpose. Every word earns its place: 'Put your virtual pet to sleep' specifies the action, and 'to restore energy' clarifies the goal. There is no redundancy or unnecessary elaboration.

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

Completeness3/5

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

Given the tool's complexity (simple mutation with no parameters) and lack of annotations/output schema, the description is minimally adequate. It explains what the tool does but doesn't cover behavioral details like side effects or energy restoration mechanics. For a mutation tool, more context on outcomes or constraints 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 no parameter documentation is needed. The description appropriately doesn't discuss parameters, focusing instead on the tool's purpose. Baseline is 4 for zero-parameter tools when the description is adequate for the action.

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

Purpose4/5

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

The description clearly states the action ('put to sleep') and the resource ('virtual pet'), with the specific purpose 'to restore energy'. It distinguishes from siblings like 'check_pet' or 'play_with_pet' by focusing on energy restoration rather than status checking or entertainment. However, it doesn't explicitly contrast with all siblings (e.g., 'feed_pet' might also restore energy).

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

Usage Guidelines3/5

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

The description implies usage context ('to restore energy'), suggesting this tool should be used when the pet's energy is low. However, it doesn't provide explicit guidance on when NOT to use it (e.g., if the pet is already sleeping) or mention alternatives like 'feed_pet' for energy restoration. The context is clear but lacks exclusion criteria or sibling comparisons.

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