Skip to main content
Glama

get_server_properties

Retrieve and display all server.properties configuration settings for Minecraft Java Edition servers, including key-value pairs and descriptions for known parameters.

Instructions

Read all server.properties settings. Returns key-value pairs with descriptions for known settings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The tool 'get_server_properties' is registered here. The async callback directly reads server properties from the manager and formats them for the user.
    server.tool(
      "get_server_properties",
      "Read all server.properties settings. Returns key-value pairs with descriptions for known settings.",
      {},
      async () => {
        const props = manager.properties.readAll();
        if (Object.keys(props).length === 0) {
          return {
            content: [
              {
                type: "text",
                text: "server.properties not found. Start the server once or use set_server_property to create it.",
              },
            ],
          };
        }
    
        const lines = Object.entries(props).map(([key, value]) => {
          const desc = SERVER_PROPERTY_DESCRIPTIONS[key];
          return desc ? `${key}=${value}  # ${desc}` : `${key}=${value}`;
        });
        return { content: [{ type: "text", text: lines.join("\n") }] };
      }
    );
Behavior3/5

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

With no annotations provided, the description carries full burden. It discloses return format ('key-value pairs') and content quality ('descriptions for known settings'), implying some settings may be undocumented. However, it lacks safety confirmation, error behavior, or performance characteristics.

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 with zero waste: first declares operation (read settings), second declares return structure. Information is front-loaded and appropriately sized for a parameterless getter tool.

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?

Given no output schema exists, the description compensates by explaining return values ('key-value pairs with descriptions'). For a simple read-only tool with no parameters, this is complete, though it could briefly mention this applies to the Minecraft server context implied by siblings.

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?

Zero parameters present. Per calibration rules, 0 params equals baseline 4. The input schema is empty object, requiring no additional semantic explanation in the description.

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 uses specific verb 'Read' targeting 'server.properties settings', clearly distinguishing from siblings 'set_server_property' and 'set_server_properties_bulk' which perform write operations. The scope 'all' clarifies it retrieves the complete configuration.

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?

While the verb 'Read' implicitly signals this is a retrieval operation versus the 'set' siblings, there is no explicit guidance on when to use this (e.g., before modifying properties) or direct reference to sibling alternatives like 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