Skip to main content
Glama
bellsanct
by bellsanct

unequip_holding_item

Remove an equipped item from a character's hand slot and return it to inventory in the MCP Dungeon Game. Specify the slot (item1 or item2) and save key to manage equipment.

Instructions

特定のスロットから持ち物を外してインベントリに戻します。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slotYes持ち物スロット: item1 または item2
save_keyYesセーブキー

Implementation Reference

  • The implementation of the unequipHoldingItem tool, which removes an item from a player's equipment slot and adds it back to their inventory.
    export async function unequipHoldingItem(slot: 'item1' | 'item2', saveKey: string): Promise<string> {
      const data = await storage.load(saveKey);
    
      if (!data.player.name) {
        return "プレイヤーが見つかりません。先に'create_player'を実行してください。";
      }
    
      if (data.player.state === 'exploring') {
        return "ダンジョン探索中は装備を変更できません。\n探索完了後に装備を整えてください。";
      }
    
      const item = data.player.equipment[slot];
    
      if (!item) {
        return `${slot === 'item1' ? '持ち物1' : '持ち物2'}スロットには何も装備されていません。`;
      }
    
      // インベントリに移動
      data.player.itemInventory.push(item as Item);
      data.player.equipment[slot] = null;
    
      await storage.save(data, saveKey);
    
      return `${slot === 'item1' ? '持ち物1' : '持ち物2'}スロットから${(item as Item).name}を外しました。`;
    }
  • The MCP tool registration and input schema definition for unequip_holding_item.
    name: 'unequip_holding_item',
    description: '特定のスロットから持ち物を外してインベントリに戻します。',
    inputSchema: {
      type: 'object',
      properties: {
        slot: {
          type: 'string',
          description: '持ち物スロット: item1 または item2',
          enum: ['item1', 'item2'],
        },
        save_key: {
          type: 'string',
          description: 'セーブキー',
        },
Behavior2/5

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

With no annotations, the description carries full burden but only states the basic action. It doesn't disclose behavioral traits like whether this requires specific game state, affects player stats, has side effects, or returns confirmation. More context is needed for a mutation tool.

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 in Japanese that directly states the tool's purpose with no wasted words. It is appropriately sized and front-loaded.

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?

For a mutation tool with no annotations and no output schema, the description is incomplete. It lacks details on effects, return values, prerequisites, or error conditions, leaving gaps in understanding how to use it effectively in context.

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

Parameters3/5

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

Schema description coverage is 100%, so parameters are well-documented in the schema. The description adds no additional meaning beyond implying 'slot' refers to equipped items and 'save_key' is for game state, which is already covered. Baseline 3 is appropriate.

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 ('外して' - remove/unequip) and the resource ('持ち物' - holding item), specifying it moves the item back to inventory. It distinguishes from 'unequip_item' by focusing on a specific slot rather than general unequipping, though not explicitly contrasted.

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 when an item is equipped in a slot and needs to be returned to inventory, but provides no explicit guidance on when to use this versus 'unequip_item' or other inventory tools. Context is clear but lacks alternatives or exclusions.

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

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/bellsanct/mcp-dungeon-game'

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