Skip to main content
Glama
bellsanct
by bellsanct

dungeon_info

Retrieve detailed information about specific dungeons in the MCP Dungeon Game, including exploration data, events, and requirements for gameplay progression.

Instructions

特定のダンジョンの詳細情報を取得します。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dungeon_idYesダンジョンのID(list_dungeonsから取得)
save_keyYesセーブキー

Implementation Reference

  • The `dungeonInfo` function retrieves and displays detailed information about a specific dungeon, including stats, enemies, bosses, and loot.
    export async function dungeonInfo(dungeonId: string, saveKey: string): Promise<string> {
      const data = await storage.load(saveKey);
      
      if (!data.player.name) {
        return "プレイヤーが見つかりません。先に'create_player'を実行してください。";
      }
    
      const dungeon = getDungeonById(dungeonId);
      
      if (!dungeon) {
        return `ダンジョン '${dungeonId}' が見つかりません。`;
      }
    
      const playerStats = calculateTotalStats(data.player.equipment);
      const actualTime = calculateDungeonTime(dungeon.baseTime, playerStats.speed);
    
      let output = `=== ${dungeon.name} ===\n\n`;
      output += `階層: ${dungeon.floors}階\n`;
      output += `推定所要時間: ${actualTime}分\n\n`;
      
      output += `出現モンスター:\n`;
      for (const enemy of dungeon.enemies) {
        output += `  ${enemy.name}\n`;
        output += `    攻撃: ${enemy.stats.attack} 防御: ${enemy.stats.defense} 速度: ${enemy.stats.speed} 運: ${enemy.stats.luck}\n`;
        output += `    ゴールド: ${enemy.goldDrop[0]}-${enemy.goldDrop[1]}\n`;
        output += `    ドロップ率: ${(enemy.equipmentDropRate * 100).toFixed(1)}%\n`;
      }
    
      output += `\nボス:\n`;
      output += `  ${dungeon.boss.name}\n`;
      output += `    攻撃: ${dungeon.boss.stats.attack} 防御: ${dungeon.boss.stats.defense} 速度: ${dungeon.boss.stats.speed} 運: ${dungeon.boss.stats.luck}\n`;
      output += `    ゴールド: ${dungeon.boss.goldDrop[0]}-${dungeon.boss.goldDrop[1]}\n`;
      output += `    ドロップ率: ${(dungeon.boss.equipmentDropRate * 100).toFixed(1)}%\n`;
    
      output += `\n入手可能な装備:\n`;
      const rarities = [...new Set(dungeon.rewardPool.map(r => r.rarity))];
      for (const rarity of rarities) {
        const items = dungeon.rewardPool.filter(r => r.rarity === rarity);
        output += `  ${rarity}: ${items.length}種類\n`;
      }
    
      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 states this is a retrieval operation ('取得します'), implying it's read-only, but doesn't confirm this explicitly or mention other behavioral traits like authentication needs, rate limits, error conditions, or what '詳細情報' (detailed information) specifically includes. For a tool with zero annotation coverage, this is insufficient.

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 purpose. It's front-loaded with the core action and resource, with no unnecessary words. However, it could be slightly more informative without losing conciseness, such as by hinting at the type of information returned.

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 context: no annotations, no output schema, and a read-focused tool with 2 required parameters, the description is incomplete. It doesn't explain what '詳細情報' includes (e.g., monsters, rewards, difficulty), whether it's safe to call repeatedly, or how errors are handled. For a tool in a game/dungeon context with siblings like 'start_dungeon', more guidance 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%, with both parameters ('dungeon_id' and 'save_key') documented in the schema. The description doesn't add any parameter-specific information beyond what's in the schema (e.g., it doesn't explain the purpose of 'save_key' or provide examples). With high schema coverage, the baseline score of 3 is appropriate as the schema does the heavy lifting.

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 '特定のダンジョンの詳細情報を取得します' (Get detailed information for a specific dungeon), which provides a clear verb ('取得します' - get/retrieve) and resource ('ダンジョンの詳細情報' - detailed dungeon information). However, it doesn't distinguish this from sibling tools like 'list_dungeons' or 'start_dungeon', which also involve dungeon-related operations. The purpose is understandable 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 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. There's no mention of prerequisites (e.g., needing to list dungeons first), when not to use it, or how it differs from similar tools like 'list_dungeons' or 'check_progress'. The agent must infer usage from the tool name and description alone.

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