Skip to main content
Glama
bellsanct
by bellsanct

create_player

Create a new player character with a unique name and save key to start playing the MCP Dungeon Game, an idle dungeon crawler with equipment collection and auto-battles.

Instructions

名前を付けて新しいプレイヤーキャラクターを作成します。ゲームごとに一度だけ実行できます。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesキャラクター名
save_keyYesセーブキー

Implementation Reference

  • The 'createPlayer' function handles character creation, including initializing stats, equipment, and gold.
    export async function createPlayer(name: string, saveKey: string): Promise<string> {
      const data = await storage.load(saveKey);
    
      if (data.player.name) {
        return `プレイヤーは既に存在します: ${data.player.name}\n'view_status'でキャラクター情報を確認してください。`;
      }
    
      data.player.name = name;
    
      // 初期装備を付与
      const starterWeapon = STARTER_EQUIPMENT.find(eq => eq.id === 'rusty_sword')!;
      const starterArmor = STARTER_EQUIPMENT.find(eq => eq.id === 'leather_armor')!;
    
      data.player.equipment.weapon = starterWeapon;
      data.player.equipment.armor = starterArmor;
      data.player.equipment.item1 = null;
      data.player.equipment.item2 = null;
      data.player.gold = 100; // 初期ゴールド
      data.player.hp = 100; // 初期HP
      data.player.maxHp = 100; // 最大HP
      data.player.itemInventory = []; // 持ち物インベントリを初期化
      data.player.state = 'idle';
    
      await storage.save(data, saveKey);
    
      return `ようこそ、${name}!\n\n初期装備:\n- ${starterWeapon.name} (攻撃力+${starterWeapon.stats.attack})\n- ${starterArmor.name} (防御力+${starterArmor.stats.defense})\n\n初期ゴールド: 100\n\n'view_status'でステータスを確認できます!`;
    }
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It mentions the 'once per game' limitation, which is useful behavioral context. However, it does not disclose other traits such as whether this is a mutation, what happens on duplicate names, or error conditions. The description adds some value but leaves gaps in behavioral disclosure.

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 two concise sentences in Japanese, front-loaded with the main purpose and followed by a usage guideline. Every sentence earns its place by providing essential information without redundancy or fluff. It is appropriately sized for the tool's complexity.

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 no annotations and no output schema, the description is moderately complete. It covers the purpose and a key usage limitation, but lacks details on behavioral traits, error handling, or return values. For a mutation tool with two parameters, it provides a basic understanding but could be more comprehensive to fully guide an agent.

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 both parameters ('name' and 'save_key') with descriptions. The description does not add any meaning beyond what the schema provides, such as explaining the purpose of 'save_key' or constraints on 'name'. Baseline 3 is appropriate as the schema handles parameter documentation adequately.

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 tool's purpose: 'create a new player character with a name' (名前を付けて新しいプレイヤーキャラクターを作成します). It specifies the action (create) and resource (player character), but does not explicitly differentiate it from sibling tools like 'init_game', which might have overlapping functionality. The description is specific but lacks sibling differentiation.

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

Usage Guidelines4/5

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

The description provides clear context for when to use this tool: 'once per game' (ゲームごとに一度だけ実行できます). This indicates a prerequisite or limitation, but it does not specify when not to use it or name alternatives among siblings. The guidance is helpful but not exhaustive regarding exclusions or 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

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