Skip to main content
Glama

plan_minestom_feature

Read-onlyIdempotent

Creates a structured plan for any Minestom feature using official patterns for bootstrap, commands, events, instances, schedulers, and threading.

Instructions

Use this when you want a Minestom feature plan grounded in official patterns for bootstrap, commands, events, instances, schedulers, and threading.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
featureTypeYesThe kind of Minestom feature you want to plan.
languageNoThe target JVM language for the implementation.java
packageNameNoBase package name for the generated outline.dev.example.minestom
targetNameYesA short feature name such as SpawnCommand or LobbyJoinListener.
useCasesNoOptional behavior notes or acceptance criteria to fold into the plan.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
featureTypeYes
filesYes
implementationStepsYes
keyApisYes
primaryTopicYes
summaryYes
supportingTopicsYes
threadSafetyNotesYes
verificationStepsYes

Implementation Reference

  • The server handler function that executes the 'plan_minestom_feature' tool logic. It parses input, builds file paths from blueprints, resolves key APIs, constructs implementation steps, and returns a validated output containing files, implementationSteps, keyApis, topics, threadSafetyNotes, and verificationSteps.
    }).server(async (args) => {
    	const { featureType, language, packageName, targetName, useCases } =
    		planMinestomFeatureInputSchema.parse(args);
    	const blueprint = getFeatureBlueprint(featureType);
    	const extension = language === "kotlin" ? "kt" : "java";
    	const packagePath = packageName.replaceAll(".", "/");
    
    	const files = blueprint.fileTemplates.map((template) => {
    		const className = template.suffix
    			? `${targetName}${template.suffix}`
    			: targetName;
    
    		return {
    			path: `src/main/${language}/${packagePath}/${className}.${extension}`,
    			purpose: template.purpose,
    		};
    	});
    
    	const keyApis = getApisBySymbols(blueprint.keyApiSymbols).map((api) => ({
    		javadocUrl: api.javadocUrl,
    		packageName: api.packageName,
    		symbol: api.symbol,
    	}));
    
    	const summary =
    		useCases.length > 0
    			? `${blueprint.summary} Prioritize these use cases: ${useCases.join("; ")}.`
    			: blueprint.summary;
    
    	return planMinestomFeatureOutputSchema.parse({
    		featureType,
    		files,
    		implementationSteps: [
    			...blueprint.implementationSteps,
    			...(useCases.length > 0
    				? [
    						`Fold the requested behavior into the design without breaking the main Minestom ownership boundary: ${useCases.join("; ")}.`,
    					]
    				: []),
    		],
    		keyApis,
    		primaryTopic: blueprint.primaryTopic,
    		summary,
    		supportingTopics: blueprint.supportingTopics,
    		threadSafetyNotes: blueprint.threadSafetyNotes,
    		verificationSteps: blueprint.verificationSteps,
    	});
    });
  • Input schema (planMinestomFeatureInputSchema) defining the expected parameters: featureType, language, packageName, targetName, and useCases.
    const planMinestomFeatureInputSchema = z.object({
    	featureType: minestomFeatureTypeSchema.describe(
    		"The kind of Minestom feature you want to plan.",
    	),
    	language: languageSchema
    		.default("java")
    		.describe("The target JVM language for the implementation."),
    	packageName: z
    		.string()
    		.default("dev.example.minestom")
    		.describe("Base package name for the generated outline."),
    	targetName: z
    		.string()
    		.describe(
    			"A short feature name such as SpawnCommand or LobbyJoinListener.",
    		),
    	useCases: z
    		.array(z.string())
    		.default([])
    		.describe(
    			"Optional behavior notes or acceptance criteria to fold into the plan.",
    		),
    });
  • Output schema (planMinestomFeatureOutputSchema) defining the structure of the tool response: featureType, files, implementationSteps, keyApis, primaryTopic, summary, supportingTopics, threadSafetyNotes, verificationSteps.
    const planMinestomFeatureOutputSchema = z.object({
    	featureType: minestomFeatureTypeSchema,
    	files: z.array(
    		z.object({
    			path: z.string(),
    			purpose: z.string(),
    		}),
    	),
    	implementationSteps: z.array(z.string()),
    	keyApis: z.array(
    		z.object({
    			javadocUrl: z.string().url(),
    			packageName: z.string(),
    			symbol: z.string(),
    		}),
    	),
    	primaryTopic: minestomTopicSchema,
    	summary: z.string(),
    	supportingTopics: z.array(minestomTopicSchema),
    	threadSafetyNotes: z.array(z.string()),
    	verificationSteps: z.array(z.string()),
    });
  • src/tools.ts:18-28 (registration)
    The tool is registered as a TanStackServerTool in the tools array. On line 25, planMinestomFeatureTool is pushed into the tools list alongside other tools.
    tools.push(
    	pingTool,
    	createGetServerInfoTool(toolNames),
    	inspectMinestomEnvironmentTool,
    	inspectMinestomBuildTool,
    	explainMinestomPatternTool,
    	lookupMinestomApiTool,
    	planMinestomFeatureTool,
    	reviewMinestomDesignTool,
    	suggestMinestomLibrariesTool,
    );
  • getFeatureBlueprint() helper used by the handler to retrieve the FeatureBlueprint for a given MinestomFeatureType. The featureBlueprints record contains fileTemplates, implementationSteps, keyApiSymbols, primaryTopic, supportingTopics, threadSafetyNotes, and verificationSteps for each feature type.
    export function getFeatureBlueprint(
    	featureType: MinestomFeatureType,
    ): FeatureBlueprint {
    	return featureBlueprints[featureType];
    }
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, covering safety and idempotency. The description adds context about 'official patterns' but does not elaborate on behavior beyond annotations. No contradictions.

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, front-loaded with the use case. Every word is necessary and there is no extraneous content.

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?

Given the complexity (5 parameters, output schema present), the description is short but sufficient to understand when to invoke. The output schema likely covers return values, so the description does not need to explain them. Slight deduction for not mentioning plan structure.

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 coverage is 100%, so the input schema already describes all parameters. The description does not add parameter-level detail but is not required to; baseline 3 is appropriate.

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 clearly states the tool's action ('plan') and resource ('Minestom feature plan') and specifies it is grounded in official patterns. It distinguishes from sibling tools like 'explain_minestom_pattern' (plan vs explain) and 'inspect_*' (plan vs inspect).

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

Usage Guidelines4/5

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

The description starts with 'Use this when you want...' providing clear use context. It implicitly differentiates from siblings but does not explicitly list exclusions or alternatives. It could benefit from mentioning when not to use or suggesting 'explain_minestom_pattern' for understanding existing patterns.

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/Azoraqua/minestom-mcp'

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