Skip to main content
Glama

server_create

Create a new Minecraft server in Crafty Controller for Java, Bedrock, or custom server types by configuring name, monitoring type, and creation parameters.

Instructions

Create a new Minecraft server in Crafty Controller. Supports Java (download jar or import), Bedrock, and custom server types.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesServer name (min 2 chars, no slashes or hashes)
monitoring_typeYesMonitoring/server type
create_typeYesServer creation type
minecraft_java_create_dataNoRequired when create_type is minecraft_java
minecraft_bedrock_create_dataNoRequired when create_type is minecraft_bedrock

Implementation Reference

  • Registration and handler implementation of the "server_create" tool.
    server.tool(
      "server_create",
      "Create a new Minecraft server in Crafty Controller. Supports Java (download jar or import), Bedrock, and custom server types.",
      {
        name: z.string().min(2).describe("Server name (min 2 chars, no slashes or hashes)"),
        monitoring_type: z
          .enum(["minecraft_java", "minecraft_bedrock", "none"])
          .describe("Monitoring/server type"),
        create_type: z
          .enum(["minecraft_java", "minecraft_bedrock", "custom"])
          .describe("Server creation type"),
        minecraft_java_create_data: z
          .object({
            create_type: z.enum(["download_jar", "import_server"]),
            download_jar_create_data: z
              .object({
                category: z.string().default("mc_java_servers"),
                type: z
                  .string()
                  .describe("Server software: paper, vanilla, fabric, forge, etc."),
                version: z.string().describe("Minecraft version, e.g. 1.21"),
                mem_min: z.number().default(1).describe("Min RAM in GB"),
                mem_max: z.number().default(2).describe("Max RAM in GB"),
                server_properties_port: z
                  .number()
                  .default(25565)
                  .describe("Server port (1-65535)"),
                agree_to_eula: z.boolean().default(true),
              })
              .optional(),
          })
          .optional()
          .describe("Required when create_type is minecraft_java"),
        minecraft_bedrock_create_data: z
          .object({
            create_type: z.enum(["download_exe", "import_server"]),
            download_exe_create_data: z
              .object({
                agree_to_eula: z.boolean().default(true),
              })
              .optional(),
          })
          .optional()
          .describe("Required when create_type is minecraft_bedrock"),
      },
      async (args) => {
        try {
          const data = await client.post("/servers", args);
          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 };
        }
      }
    );
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool creates servers but lacks details on permissions required, whether it's idempotent, error handling, rate limits, or what happens on success (e.g., returns a server ID). This is a significant gap for a creation tool with complex parameters.

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 that front-loads the core purpose. It could be slightly more structured by separating server type details, but it avoids redundancy and wastes no words.

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?

For a complex creation tool with 5 parameters, nested objects, and no output schema, the description is inadequate. It doesn't explain the return value, error conditions, or behavioral aspects like authentication needs. With no annotations and rich schema, the description should provide more operational context to be complete.

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 all parameters thoroughly. The description adds minimal value by mentioning server types (Java, Bedrock, custom) which aligns with 'create_type' enum values, but doesn't provide additional context beyond what's in the schema. Baseline 3 is appropriate when schema does the heavy lifting.

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 ('Create a new Minecraft server') and resource ('in Crafty Controller'), specifying supported server types (Java, Bedrock, custom). It doesn't explicitly differentiate from sibling tools like 'server_clone' or 'server_update', but the verb 'Create' is distinct from operations like 'Clone' or 'Update'.

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?

No guidance is provided on when to use this tool versus alternatives like 'server_clone' for duplicating existing servers or 'server_update' for modifying servers. The description mentions supported server types but doesn't specify prerequisites, constraints, or exclusions for usage.

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