Skip to main content
Glama
tamo2918

Minecraft Server MCP

by tamo2918
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

set_weather

Change Minecraft server weather conditions to clear, rain, or thunder with optional duration control for server administration.

Instructions

Set the weather. Options: clear, rain, thunder.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
weatherYesWeather type
durationNoDuration in seconds (optional)

Implementation Reference

  • src/tools/command-tools.ts:123-134 (handler)
    The handler function for 'set_weather' that constructs and sends the RCON command.
    async ({ weather, duration }) => {
  const cmd = duration
    ? `weather ${weather} ${duration}`
    : `weather ${weather}`;
  try {
    const response = await manager.rcon.send(cmd);
    return { content: [{ type: "text", text: response }] };
  } catch (error) {
    return {
      content: [
        {
          type: "text",
  • src/tools/command-tools.ts:116-122 (schema)
    Input schema definition for the 'set_weather' tool using Zod.
    {
  weather: z.enum(["clear", "rain", "thunder"]).describe("Weather type"),
  duration: z
    .number()
    .optional()
    .describe("Duration in seconds (optional)"),
},
  • src/tools/command-tools.ts:113-115 (registration)
    Registration of the 'set_weather' tool within the MCP server instance.
    server.tool(
  "set_weather",
  "Set the weather. Options: clear, rain, thunder.",

Tool Definition Quality

C2.9/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. States the action but omits critical behavioral details: scope (affects entire world or specific players?), persistence (permanent or temporary?), default behavior when optional 'duration' is omitted, and whether this triggers immediately or has transition effects.

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?

Extremely brief two-sentence structure with no filler. Front-loaded with the action. Minor inefficiency in enumerating options already defined in schema enum, but remains readable and scannable.

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

Completeness3/5

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

Adequate for a simple 2-parameter setter with complete schema documentation. However, lacks explanation of side effects, return behavior (if any), and the semantic implication of omitting the optional duration parameter, leaving operational gaps for the agent.

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 has 100% description coverage with 'Weather type' and 'Duration in seconds (optional)'. Description lists the enum values ('clear, rain, thunder') which duplicates schema information but adds no additional semantic context about parameter formats, defaults, or interdependencies. Baseline 3 appropriate for high-coverage schema.

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?

Clear verb ('Set') and resource ('weather') with specific enum values listed. However, lacks explicit domain context (Minecraft/simulation) that would fully distinguish it from conceptual siblings like set_time or set_block, though the specific weather options provide implicit differentiation.

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 on when to invoke this tool versus alternatives (e.g., when to use weather vs time controls), no mention of prerequisites, and no warnings about impact on gameplay or player experience.

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