Skip to main content
Glama

set_server_properties_bulk

Configure multiple Minecraft server settings simultaneously to set up new servers or modify world generation parameters.

Instructions

Set multiple server.properties values at once. Useful for configuring a new server or changing world generation settings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
propertiesYesObject of key-value pairs to set (e.g., { 'gamemode': 'creative', 'difficulty': 'hard' })

Implementation Reference

  • The tool registration and handler implementation for set_server_properties_bulk. It uses z.record(z.string(), z.string()) for input validation and calls manager.properties.setMultiple to update the configuration.
    server.tool(
      "set_server_properties_bulk",
      "Set multiple server.properties values at once. Useful for configuring a new server or changing world generation settings.",
      {
        properties: z
          .record(z.string(), z.string())
          .describe("Object of key-value pairs to set (e.g., { 'gamemode': 'creative', 'difficulty': 'hard' })"),
      },
      async ({ properties }) => {
        manager.properties.setMultiple(properties);
        const lines = Object.entries(properties).map(
          ([k, v]) => `  ${k}=${v}`
        );
        return {
          content: [
            {
              type: "text",
              text: `Set ${lines.length} properties:\n${lines.join("\n")}\n\n⚠️ Restart the server for changes to take effect.`,
            },
          ],
        };
      }
    );
Behavior2/5

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

No annotations provided. Description omits critical behavioral details for a bulk config mutation: whether changes are atomic, require server restart, validate property keys, or persist immediately. 'Configuring a new server' implies pre-startup use but doesn't clarify runtime behavior.

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 sentences, zero waste. First sentence establishes core purpose with 'bulk' qualifier; second provides concrete usage context. Well front-loaded.

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 parameter definition given 100% schema coverage, but lacking behavioral disclosure expected for a mutation tool with no annotations or output schema. Should clarify restart requirements and validation behavior.

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 has 100% coverage with clear example. Description adds domain context ('server.properties', 'world generation settings') but largely relies on schema's existing example (gamemode, difficulty). Baseline 3 appropriate when schema carries definition.

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?

Clear specific verb 'Set' + resource 'server.properties' + scope 'multiple at once'. The 'bulk' in the name and 'multiple' in description clearly distinguishes from sibling tool 'set_server_property' (singular).

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 contextual usage hints ('Useful for configuring a new server or changing world generation settings') but lacks explicit when-not guidance or comparison to singular alternative 'set_server_property'.

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