Skip to main content
Glama

mc_scaffold

Create a complete Minecraft mod or plugin project from a bundled template, generating Gradle scripts, source files, metadata, and wrapper for Paper, Fabric, Forge, NeoForge, or Spigot.

Instructions

Create a new Minecraft project from bundled template. Generates complete Gradle project: build scripts, main class, plugin/mod metadata, and Gradle wrapper. Supported platforms: paper, fabric, forge, neoforge, spigot.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "platform": "<platform>",
      "targetDir": "<targetDir>",
      "name": "<name>",
      "packageName": "<packageName>",
      "minecraftVersion": "<minecraftVersion>"
    },
    "name": "mc_scaffold"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesProject name in lowercase kebab-case (e.g. my-plugin)
platformYesProject platform
targetDirYesAbsolute path of the new project root; must not exist or be empty
javaVersionNoJava level (8/17/21/25). Omit for era default.
packageNameYesJava package name, e.g. com.example.myplugin
minecraftVersionYesTarget MC version, e.g. 1.7.10, 1.12.2, 1.20.1, 1.21.8, 26.3

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. "Bundled template" usefully implies the scaffold comes from local resources rather than a network fetch, and the listed artifacts signal the scope of writes, but the description never states whether existing files could be touched, whether the Gradle wrapper download requires network access, or what happens on partial failure.

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?

Two tight sentences, front-loaded with the core action and followed by the concrete output inventory. Nothing is repeated and no filler appears.

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 six-parameter, five-required creation tool with full schema coverage, the description covers purpose and generated artifacts adequately. The remaining gap is the absence of any output schema combined with no statement of what the call returns (paths, summary, next steps), which an agent would want after scaffolding.

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 all six parameters (including the five required ones) are already documented with examples and constraints. The description's platform enumeration merely restates the enum values and adds no semantics about javaVersion defaults or the relationship between minecraftVersion and platform that the schema doesn't already give.

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 uses a specific verb and resource ("Create a new Minecraft project") and enumerates the concrete artifacts produced (build scripts, main class, plugin/mod metadata, Gradle wrapper), so the agent knows exactly what the call yields. It stops short of differentiating from the sibling mc_gradle, which also concerns Gradle scaffolding, leaving some ambiguity about which tool owns post-creation Gradle work.

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 only implied by "Create a new Minecraft project from bundled template"; there is no explicit statement of when to prefer this over mc_gradle or mc_read_reference, and no stated prerequisites such as requiring an empty target directory or whether a follow-up build step is expected. The agent can infer the greenfield-project scenario but gets no routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.