Skip to main content
Glama

set_server_property

Modify Minecraft server configuration properties like gamemode, difficulty, or max-players. Changes require server restart to take effect.

Instructions

Set a server.properties value. The server must be restarted for changes to take effect. Common properties: gamemode, difficulty, level-seed, level-type, max-players, view-distance, motd, online-mode, pvp, spawn-protection.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesProperty key (e.g., 'level-seed', 'gamemode', 'difficulty')
valueYesProperty value

Implementation Reference

  • The handler logic for the 'set_server_property' tool, which updates the server property via the manager and notifies the user to restart.
    async ({ key, value }) => {
      manager.properties.set(key, value);
      const desc = SERVER_PROPERTY_DESCRIPTIONS[key];
      let msg = `Set ${key}=${value}`;
      if (desc) msg += `\n(${desc})`;
      msg += "\n\n⚠️ Restart the server for this change to take effect.";
      return { content: [{ type: "text", text: msg }] };
    }
  • The MCP tool registration for 'set_server_property'.
    server.tool(
      "set_server_property",
      "Set a server.properties value. The server must be restarted for changes to take effect. Common properties: gamemode, difficulty, level-seed, level-type, max-players, view-distance, motd, online-mode, pvp, spawn-protection.",
      {
        key: z.string().describe("Property key (e.g., 'level-seed', 'gamemode', 'difficulty')"),
        value: z.string().describe("Property value"),
      },
      async ({ key, value }) => {
        manager.properties.set(key, value);
        const desc = SERVER_PROPERTY_DESCRIPTIONS[key];
        let msg = `Set ${key}=${value}`;
        if (desc) msg += `\n(${desc})`;
        msg += "\n\n⚠️ Restart the server for this change to take effect.";
        return { content: [{ type: "text", text: msg }] };
      }
    );
Behavior3/5

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

No annotations provided, so description carries full burden. Discloses the restart requirement (major behavioral trait). Missing: validation behavior (does it check valid keys/values?), error conditions, whether changes are persistent across sessions, or atomicity guarantees.

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?

Three tight sentences: purpose, critical constraint, examples. No redundancy, logically sequenced (action → consequence → reference). Front-loaded with the core verb.

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?

Adequate for a simple 2-parameter setter, with good examples. Gaps: no mention of return value or success confirmation (particularly important given no output schema), and no error scenarios (e.g., invalid property keys).

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 has 100% coverage with basic descriptions. Description adds significant semantic value by enumerating common properties (gamemode, difficulty, level-seed, etc.), giving users concrete valid inputs for the 'key' parameter beyond the generic schema description.

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?

Clear specific action: 'Set a server.properties value' identifies the exact file/resource. The restart requirement implicitly distinguishes from runtime setters like set_gamemode. However, it lacks explicit contrast with set_server_properties_bulk (singular vs plural scope) which could confuse users.

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?

Provides critical operational constraint: 'server must be restarted for changes to take effect.' However, fails to explicitly guide against alternatives (e.g., when to use set_server_properties_bulk for batch updates vs individual calls, or that set_gamemode applies immediately without restart).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tamo2918/Minecraft-Server-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server