Skip to main content
Glama
bellsanct
by bellsanct

equip_holding_item

Equip consumable items from inventory to use during dungeon exploration. Items include healing herbs for HP recovery and charms to avoid random events.

Instructions

インベントリから持ち物を装備します。持ち物には薬草(HP回復)やおまもり(イベント回避)があります。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
item_idYes装備する持ち物のID(インベントリに表示)
slotYes持ち物スロット: item1 または item2
save_keyYesセーブキー

Implementation Reference

  • Implementation of equipHoldingItem, which assigns an item from the item inventory to one of the player's holding slots (item1 or item2).
    export async function equipHoldingItem(itemId: string, 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 itemIndex = data.player.itemInventory.findIndex(item => item.id === itemId);
    
      if (itemIndex === -1) {
        return `ID '${itemId}' の持ち物がインベントリに見つかりません。`;
      }
    
      const item = data.player.itemInventory[itemIndex];
    
      // 現在装備中のアイテムがあれば外す
      if (data.player.equipment[slot]) {
        const currentItem = data.player.equipment[slot] as Item;
        data.player.itemInventory.push(currentItem);
      }
    
      // 新しいアイテムを装備
      data.player.equipment[slot] = item;
      data.player.itemInventory.splice(itemIndex, 1);
    
      await storage.save(data, saveKey);
    
      return `${item.name}を${slot === 'item1' ? '持ち物1' : '持ち物2'}スロットに装備しました!\n効果: ${item.description}`;
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral context. It implies this is a mutation (equipping changes state) but doesn't disclose permissions needed, whether it's reversible, side effects, or response format. The examples hint at item effects but don't explain how equipping affects gameplay.

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

Conciseness4/5

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

The description is appropriately concise with two sentences. The first states the core purpose, and the second provides helpful examples of holding items. However, it could be more front-loaded by integrating the examples into the purpose statement for better clarity.

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 what happens after equipping (e.g., effects on status, inventory changes), error conditions, or interaction with other tools like 'view_inventory'. The examples add some context but don't compensate for the overall gaps.

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 the schema already documents all three parameters thoroughly. The description adds no parameter-specific information beyond what's in the schema, such as how item_id relates to inventory or the significance of save_key. Baseline 3 is appropriate when schema does the heavy lifting.

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 ('装備します' - equip) and resource ('持ち物' - holding item) from the inventory. It distinguishes from 'equip_item' by specifying it's for holding items (consumables/accessories) rather than equipment, though it doesn't explicitly mention the sibling 'unequip_holding_item'.

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 'equip_item' or 'unequip_holding_item'. It mentions examples of holding items (herbs for HP recovery, charms for event avoidance) but doesn't specify prerequisites, timing, or constraints for usage.

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