Skip to main content
Glama

server_clone

Clone an existing Minecraft server by providing its ID. Use this tool to create a duplicate server when the original is not running.

Instructions

Clone an existing Minecraft server (server must not be running)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
server_idYesServer ID or UUID

Implementation Reference

  • The tool is registered dynamically within a loop. The handler logic performs a POST request to the Crafty server API using the server ID.
    server.tool(
      name,
      description,
      serverIdSchema,
      async ({ server_id }) => {
        try {
          const data = await client.post(`/servers/${server_id}/action/${action}`);
          return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
        } catch (error) {
          const msg = error instanceof Error ? error.message : String(error);
          return { content: [{ type: "text", text: `Error: ${msg}` }], isError: true };
        }
      }
    );
  • The tool "server_clone" is registered in the `actions` array which is then iterated to create the tool.
      { name: "server_clone", action: "clone_server", description: "Clone an existing Minecraft server (server must not be running)" },
    ];
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 server must not be running, which is a useful behavioral constraint. However, it fails to disclose critical traits like what gets cloned (e.g., settings, files), permissions required, rate limits, or what the clone operation entails (e.g., creates a new server instance). This leaves significant gaps for a mutation tool.

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 a single, efficient sentence with no wasted words. It front-loads the core action ('Clone an existing Minecraft server') and adds a necessary constraint ('server must not be running') concisely. Every part earns its place.

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 cloning operation (a mutation tool with no annotations and no output schema), the description is incomplete. It lacks details on what is cloned, the result (e.g., returns a new server ID), error conditions, or dependencies. For a tool that likely creates a new resource, this is inadequate to guide an agent fully.

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 the parameter 'server_id' fully documented in the schema. The description does not add any additional meaning beyond the schema, such as examples or constraints. With high schema coverage, the baseline is 3, as the description doesn't compensate but doesn't need to heavily.

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 action ('Clone') and resource ('an existing Minecraft server'), specifying the server must not be running. It distinguishes from siblings like 'server_create' by focusing on duplication rather than creation from scratch. However, it doesn't explicitly differentiate from other cloning-related tools (none in siblings), keeping it at 4.

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?

The description implies usage by stating the server must not be running, which provides some context for when to use it. However, it lacks explicit guidance on when to choose this over alternatives like 'server_create' or prerequisites beyond the running state. No clear exclusions or named alternatives 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/HadiCherkaoui/crafty-mcp'

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