Skip to main content
Glama

get_game_rules

Retrieve all current game rules for a Minecraft world using RCON commands. This tool helps server administrators view and manage world settings while the server is running.

Instructions

Get all game rules for the current world via RCON. Server must be running.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The implementation of the get_game_rules tool, which calls the manager.rcon.send("gamerule") method to fetch game rules.
    server.tool(
      "get_game_rules",
      "Get all game rules for the current world via RCON. Server must be running.",
      {},
      async () => {
        try {
          const response = await manager.rcon.send("gamerule");
          return { content: [{ type: "text", text: response }] };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Failed to get game rules: ${error instanceof Error ? error.message : String(error)}\nIs the server running with RCON enabled?`,
              },
            ],
            isError: true,
          };
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses the RCON transport method and server state dependency, but omits details about return format, error conditions, or read-only safety characteristics that would help an agent predict outcomes.

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: the first front-loads the action and scope, the second provides a critical prerequisite. Every word earns its place with no redundancy.

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?

While the description adequately covers the invocation requirements for this zero-parameter tool, it lacks return value documentation. Given the absence of an output schema, mentioning the expected structure (e.g., key-value pairs) would have completed the picture.

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?

The input schema contains zero parameters, which per guidelines warrants a baseline score of 4. The description appropriately does not invent parameter documentation where none exist.

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 a specific verb ('Get') and resource ('game rules for the current world'), clearly distinguishing it from sibling 'set_game_rule'. It also specifies the transport mechanism ('via RCON'), adding precise operational context.

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?

The description states the prerequisite 'Server must be running,' which guides when the tool can be invoked. However, it lacks explicit guidance on when to prefer this over alternatives like 'set_game_rule' or what to do if the server is offline.

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