Skip to main content
Glama
bellsanct
by bellsanct

list_dungeons

Retrieve available dungeons and their details for the MCP Dungeon Game idle crawler using your save key. View dungeon information to plan exploration and equipment collection.

Instructions

利用可能なすべてのダンジョンとその情報を一覧表示します。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
save_keyYesセーブキー

Implementation Reference

  • The listDungeons function fetches all available dungeons using getAllDungeons() and formats them into a descriptive string including floor count, duration, enemies, boss, and loot rarity. It takes a saveKey to verify the player's existence before returning the list.
    export async function listDungeons(saveKey: string): Promise<string> {
      const data = await storage.load(saveKey);
      
      if (!data.player.name) {
        return "プレイヤーが見つかりません。先に'create_player'を実行してください。";
      }
    
      const dungeons = getAllDungeons();
      const playerStats = calculateTotalStats(data.player.equipment);
    
      let output = `=== 利用可能なダンジョン ===\n\n`;
    
      for (const dungeon of dungeons) {
        const actualTime = calculateDungeonTime(dungeon.baseTime, playerStats.speed);
        
        output += `[${dungeon.id}] ${dungeon.name}\n`;
        output += `  階層: ${dungeon.floors}階\n`;
        output += `  所要時間: ${actualTime}分 (基本: ${dungeon.baseTime}分)\n`;
        output += `  出現モンスター: ${dungeon.enemies.map(e => e.name).join(', ')}\n`;
        output += `  ボス: ${dungeon.boss.name}\n`;
        output += `  報酬レアリティ: ${[...new Set(dungeon.rewardPool.map(r => r.rarity))].join(', ')}\n`;
        output += '\n';
      }
    
      output += `詳細情報: 'dungeon_info <dungeon_id>'\n`;
      output += `探索開始: 'start_dungeon <dungeon_id>'`;
    
      return output;
    }
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 of behavioral disclosure. It mentions listing dungeons and their information, but does not describe key traits like whether this is a read-only operation, if it requires authentication via 'save_key', potential rate limits, or the format of the returned data. This leaves significant gaps for an agent to understand how to invoke it correctly.

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 a single, efficient sentence in Japanese that directly states the tool's function. It is front-loaded and wastes no words, though it could be slightly more informative without losing conciseness. The structure is clear but minimal.

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 complexity of a tool that lists dungeons with information, no annotations, no output schema, and 1 parameter, the description is incomplete. It does not cover behavioral aspects like data format, pagination, or error handling, and it lacks differentiation from sibling tools. This makes it inadequate for an agent to fully understand the tool's context and usage.

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?

The input schema has 100% description coverage, with the parameter 'save_key' documented as 'セーブキー' (save key). The description does not add any meaning beyond this, such as explaining what a save key is or how it's used. Given the high schema coverage, the baseline score of 3 is appropriate, as the schema handles the parameter documentation adequately.

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 ('list all available dungeons and their information'), which is clear but vague. It specifies the verb ('list') and resource ('dungeons'), but does not distinguish it from sibling tools like 'dungeon_info' or 'start_dungeon', leaving ambiguity about scope or differentiation.

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. It does not mention prerequisites, context, or exclusions, such as how it differs from 'dungeon_info' (which might get details for a specific dungeon) or 'start_dungeon' (which might initiate an adventure).

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