Skip to main content
Glama
bellsanct
by bellsanct

start_dungeon

Begin time-based dungeon exploration in an idle crawler game. Start adventures to collect equipment and trigger auto-battles, then return later to check progress.

Instructions

ダンジョンの探索を開始します。時間ベースの活動なので、後で確認する必要があります。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dungeon_idYes探索するダンジョンのID
save_keyYesセーブキー

Implementation Reference

  • The startDungeon function validates player state and dungeon existence, calculates duration based on player stats, updates the player state to 'exploring' with currentDungeon details, and saves the progress.
    export async function startDungeon(dungeonId: string, saveKey: string): Promise<string> {
      const data = await storage.load(saveKey);
      
      if (!data.player.name) {
        return "プレイヤーが見つかりません。先に'create_player'を実行してください。";
      }
    
      if (data.player.currentDungeon) {
        const remaining = Math.max(0, data.player.currentDungeon.estimatedEndTime - Date.now());
        const minutes = Math.ceil(remaining / 60000);
        return `既にダンジョンを探索中です!\n残り時間: 約${minutes}分\n\n'check_progress'で進行状況を確認できます。`;
      }
    
      const dungeon = getDungeonById(dungeonId);
      
      if (!dungeon) {
        return `ダンジョン '${dungeonId}' が見つかりません。`;
      }
    
      const playerStats = calculateTotalStats(data.player.equipment);
      const actualTime = calculateDungeonTime(dungeon.baseTime, playerStats.speed);
    
      const startTime = Date.now();
      const estimatedEndTime = startTime + (actualTime * 60 * 1000);
    
      data.player.currentDungeon = {
        dungeonId,
        startTime,
        estimatedEndTime,
        battleLog: [],
        events: []
      };
      data.player.state = 'exploring';
    
      await storage.save(data, saveKey);
    
      return `🗡️  ${dungeon.name}の探索を開始しました!\n\n推定完了時刻: ${actualTime}分後\n\n'check_progress'で進行状況を確認できます。`;
    }
Behavior2/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 activity is time-based and requires later checking, which adds some behavioral context, but it doesn't disclose critical details like whether this is a read-only or destructive operation, authentication needs, rate limits, or what happens upon invocation. The description is insufficient for a mutation tool with no annotation coverage.

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 concise with two sentences that convey key information without unnecessary details. It's front-loaded with the main action, but the second sentence could be more integrated to improve flow. Overall, it's efficient with minimal waste.

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 likely involves mutation (starting an activity) with no annotations and no output schema, the description is incomplete. It lacks details on what the tool returns, error conditions, or how it interacts with other tools like 'check_progress'. For a tool with 2 required parameters and potential side effects, more context is needed.

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 ('dungeon_id' and 'save_key') with descriptions. The description doesn't add any meaning beyond what the schema provides, such as explaining parameter interactions or usage examples. Baseline 3 is appropriate when the schema handles parameter documentation.

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 states the tool's purpose as 'starts dungeon exploration' and mentions it's a time-based activity, which provides basic clarity. However, it doesn't specify what resources are affected or how this differs from similar tools like 'init_game' or 'check_progress', making it somewhat vague rather than specific.

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 mentions that this is a time-based activity requiring later checking, which implies some context, but it doesn't explicitly state when to use this tool versus alternatives like 'init_game' for starting a game or 'check_progress' for monitoring. No guidance on prerequisites or exclusions is provided.

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