minecraft-mcp

by IotA-asce

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

Set weather

set_weather

Set the weather in a Minecraft world to clear, rain, or thunder, with optional world and player parameters.

Instructions

Set the weather for a world (default: the player's world).

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
`world`	No	World name (defaults to the player's current world)
`player`	No	Online player name (defaults to the first online player)
`weather`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 7, 2026

TDQS

A3.5/5.0

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 only states the basic action and default world; it does not mention whether the change is global, persistent, impacts all players, or requires permissions. This is a minimal disclosure that leaves significant gaps.

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 sentence, front-loaded with the action, and contains no extraneous words. It is appropriately sized for the tool's simplicity.

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?

Given the simple tool and no output schema, the description covers the core action and default world. However, it omits any mention of side effects on existing weather, whether the change is permanent, or how players experience it. For a tool without annotations, a little more behavioral context would be beneficial, but it is not severely incomplete.

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 schema already documents 67% of parameters (world and player), and the description adds the default world behavior ('default: the player's world'), which adds value. However, it does not clarify the weather enum options or the player default beyond what the schema provides, so the incremental contribution is moderate.

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 verb 'Set' and the resource 'weather', scoped to 'a world', with a helpful default note. It distinguishes from sibling tools like get_time_weather, which retrieves conditions rather than changing them.

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?

The description implies the usage context (changing weather) but does not explicitly contrast with alternatives like get_time_weather or set_time, nor does it state when not to use the tool. The default-world information is a small but useful contextual hint.

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