Skip to main content
Glama

Set difficulty

set_difficulty
Idempotent

Change the main world's difficulty to peaceful, easy, normal, or hard; choose peaceful to remove hostile mobs.

Instructions

Change the difficulty of the main world. 'peaceful' removes hostile mobs.

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": {
      "level": "<level>"
    },
    "name": "set_difficulty"
  }
}

Input Schema

NameRequiredDescriptionDefault
levelYesNew difficulty.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare this is a non-readonly, non-destructive, idempotent operation, so the bar is lower. The description still contributes a real behavioral side effect not present in the annotations: selecting 'peaceful' removes hostile mobs, which warns the agent of a consequential state change. It stops short of noting whether existing mobs are despawned immediately or whether the change persists across restarts.

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?

Two short sentences with no wasted wording; the core action is front-loaded and the clarifying note follows. Nothing is padded or repeated from the title.

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 one-parameter tool with full schema coverage, complete annotations, and an output schema that handles return values, the description covers what is needed to invoke it correctly. Minor gaps remain around scope (which world/dimension is 'main') and prerequisites, but they are unlikely to block correct use.

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

Parameters4/5

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

Schema coverage is 100% and the single parameter is a self-explanatory enum, so the baseline is 3. The description earns an extra point by explaining the practical consequence of the 'peaceful' value, adding meaning beyond the bare enum list.

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 and resource ('Change the difficulty of the main world'), which distinguishes it from the many set_* siblings that mutate gamemode, time, weather, or gamerules. It does not explicitly name or contrast an alternative, so it stops short of a 5.

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?

There is no when-to-use or when-not-to-use guidance, and no mention of related tools such as gamerule or gamemode settings that also affect mob behavior. The agent must infer applicability from the purpose sentence alone.

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