Skip to main content
Glama

game_set_environment

Destructive

Override a player's or server's client weather and clock time, or reset both to default values.

Instructions

Override client weather and/or clock time, or reset both

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "game_set_environment"
  }
}

Input Schema

NameRequiredDescriptionDefault
hourNo
resetNo
minuteNo
playerNo
serverNo
weatherNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, so the mutation profile is known; the description adds only the existence of a reset mode. It does not disclose whether an override persists across sessions, whether it applies globally or per-player, what happens to unspecified fields during an override, or whether reset clears weather, time, or both simultaneously.

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?

Eleven words, front-loaded with the action and its targets, with the alternate reset mode appended. There is no filler or redundancy.

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

Completeness2/5

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

For a destructive, six-parameter mutation tool with no parameter documentation and no output schema, the description is far too thin. The two scoping parameters and the interaction between reset and the value parameters are entirely undocumented, which is exactly the information an agent needs before calling it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across six parameters, so the description must compensate and largely fails. It implicitly covers weather, hour/minute, and reset, but never mentions the 'player' or 'server' parameters, leaving the agent unable to tell whether omitting them scopes the change globally or is invalid.

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?

States a specific verb ('Override') and two concrete resources ('client weather and/or clock time'), plus a second mode ('reset both'). An agent can distinguish this from generic siblings like game_execute_command or game_teleport, though 'client' scope is ambiguous given the presence of player/server parameters.

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?

The description contrasts override vs. reset but gives no when-to-use guidance, no prerequisites, and no indication of how this relates to alternatives such as game_execute_command. Nothing tells the agent when an override is preferable to running a raw command.

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