minecraft-mcp-server

set_weather

Set the current Minecraft weather to clear, rain, or thunder. Optionally specify a duration in seconds to control how long the weather condition persists.

Instructions

Set the weather to clear, rain, or thunder with optional duration.

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": {
      "weather": "<weather>"
    },
    "name": "set_weather"
  }
}

Input Schema

Name	Required	Description	Default
`weather`	Yes	Weather type to set
`durationSeconds`	No	Duration in seconds (optional)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 10, 2026

TDQS

A3.8/5.0

Behavior2/5

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

There are no annotations, so the description must disclose behavioral traits. The one-sentence description only restates the action and the optional duration, without covering what happens if duration is omitted, whether the effect is persistent, or any side effects. This leaves significant behavioral ambiguity for an AI agent.

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, focused sentence with no filler. It front-loads the action and lists the accepted values compactly.

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 tool with only two parameters and no output schema, the description covers the basic action and parameter meanings. It would benefit from clarifying the default duration behavior, but it is sufficient for a straightforward setter.

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?

The input schema describes both parameters with 100% coverage, so the description does not need to add parameter details. It does repeat 'clear, rain, or thunder' and 'optional duration' but provides no extra semantic value beyond the schema.

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 uses the verb 'Set' with a specific resource (weather) and enumerates the exact values (clear, rain, thunder), making the tool's purpose unmistakable. This clearly distinguishes it from sibling tools like set_time and set_gamerule.

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?

It provides clear context that this tool is for changing the weather condition, and includes the optional duration parameter. However, it does not explicitly state when to prefer it over alternatives or mention any prerequisites.

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

Deploy Server