Skip to main content
Glama

list_worlds

Lists all Minecraft worlds in the server directory with their file sizes for inventory management and storage optimization.

Instructions

List all Minecraft worlds in the server directory with their sizes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The `list_worlds` tool registration and handler implementation. It uses `worldManager.listWorlds()` to fetch the worlds and formats the output.
    server.tool(
      "list_worlds",
      "List all Minecraft worlds in the server directory with their sizes.",
      {},
      async () => {
        const worlds = worldManager.listWorlds();
        if (worlds.length === 0) {
          return {
            content: [
              {
                type: "text",
                text: "No worlds found. Start the server to generate one, or use setup_world to configure generation settings.",
              },
            ],
          };
        }
    
        const lines: string[] = [];
        for (const name of worlds) {
          const size = worldManager.getWorldSize(name);
          const info = await worldManager.getWorldInfo(name).catch(() => null);
          const details = info
            ? ` | Seed: ${info.seed} | GameType: ${["Survival", "Creative", "Adventure", "Spectator"][info.gameType] ?? info.gameType} | Spawn: ${info.spawnX},${info.spawnY},${info.spawnZ}`
            : "";
          lines.push(`📁 ${name} (${size.toFixed(1)} MB)${details}`);
        }
        return { content: [{ type: "text", text: lines.join("\n") }] };
      }
    );
Behavior3/5

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

With no annotations provided, the description carries the full disclosure burden. It successfully specifies that world 'sizes' are included in the output, but does not explicitly confirm read-only safety, describe the output format (array/object), or mention behavior when no worlds exist.

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?

Single sentence with zero waste. Every word earns its place: action verb ('List'), scope ('all'), resource ('Minecraft worlds'), location ('server directory'), and return fields ('sizes'). Perfectly front-loaded and sized for a parameterless tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a parameterless discovery tool with no output schema, the description adequately covers the essential operation. It would benefit from mentioning the output structure (list/array format) or confirming it returns an empty list versus error when no worlds exist, but is sufficient for invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Zero parameters are required, which per the guidelines establishes a baseline score of 4. The description appropriately focuses on the operation behavior rather than inventing parameter documentation where none exist in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('List'), clear resource ('Minecraft worlds'), and scope ('in the server directory with their sizes'). It contextually distinguishes from siblings like list_players, list_backups, and get_world_info (singular) by emphasizing 'all' worlds and including size metadata.

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

Usage Guidelines3/5

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

Usage is implied by the scope ('all' worlds for discovery/enumeration), but there is no explicit 'when to use' guidance contrasting it with get_world_info (for single world details) or setup_world. No prerequisites or error conditions are mentioned.

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/tamo2918/Minecraft-Server-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server