Skip to main content
Glama

Save worlds

save_worlds
Idempotent

Save all Minecraft worlds and player data to disk immediately; set players to false to save only worlds.

Instructions

Save every world, and player data, to disk now. Not needed before restart_server, which saves on its own. Needs server:control.

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": "save_worlds"
  }
}

Input Schema

NameRequiredDescriptionDefault
playersNofalse saves only the worlds

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv4.2.1
    • addedInput schema / properties / players / description
      Added value: +"false saves only the worlds"
  2. First observedv4.1.0

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already mark this as idempotent, non-destructive, and not read-only. The description adds useful behavior beyond the annotations: it saves player data as well as worlds, requires server:control, and is redundant before restart_server.

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 three short sentences with the main action front-loaded, followed by the key exclusion and permission requirement. There is no wasted text.

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

Completeness5/5

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

For a simple, idempotent save tool with annotations and a fully described single parameter, the description covers what is saved, when it is unnecessary, and the required permission. No output schema is needed or expected.

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 coverage is 100% and the players parameter is already documented in the schema as saving only worlds when false. The description does not add further parameter semantics beyond what the schema already provides.

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 states a specific verb and resource: save every world and player data to disk now. It also distinguishes itself from restart_server by noting that restart_server saves on its own.

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 clearly gives an exclusion case: not needed before restart_server, which already saves. It also states the prerequisite server:control, but it does not spell out broader positive cases beyond a general need to persist state now.

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