Skip to main content
Glama

Set weather

set_weather
Idempotent

Changes the Minecraft main world's weather to clear, rain, or thunder, with an optional duration for how long the condition lasts.

Instructions

Change the weather in the main world to clear, rain or thunder, optionally for a set 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": {
      "condition": "<condition>"
    },
    "name": "set_weather"
  }
}

Input Schema

NameRequiredDescriptionDefault
conditionYesNew weather.
duration_secondsNoHow long it lasts; default: the server decides.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, idempotent, non-destructive, non-open-world mutation, and the description is consistent with that. The description adds the 'main world' scope, but it never says what happens when the duration expires or whether the setting persists across restarts, which would be genuinely useful context for a state-changing tool.

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?

One front-loaded sentence with no filler, though it slightly duplicates information already carried by the enum and parameter descriptions rather than spending that space on new behavior.

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 two-parameter tool with full schema coverage, annotations, and an output schema, the description covers purpose and scope adequately; only the post-duration revert behavior is left unexplained.

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 both parameters are already fully documented, including bounds and the server-decided default. The description only restates the enum values and the optional duration, adding no syntax or behavioral meaning 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?

States a specific verb ('Change') plus the exact resource ('the weather in the main world') and enumerates the three valid outcomes, so an agent can instantly tell it apart from set_time or set_difficulty siblings.

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: it's obvious you call this when you want different weather, but there is no explicit when-to-use, when-not, or prerequisite (e.g., permissions/operator level) guidance.

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