Skip to main content
Glama

Get game rule

get_gamerule
Read-onlyIdempotent

Retrieve the current value of a Minecraft game rule in the main world as a string, so agents can check settings like keep_inventory or mob_griefing before making changes.

Instructions

Current value of a game rule in the main world, as a string.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "rule": "<rule>"
    },
    "name": "get_gamerule"
  }
}

Input Schema

NameRequiredDescriptionDefault
ruleYesGame rule such as 'keep_inventory' or 'mob_griefing' (legacy names like keepInventory work too).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so safety is fully covered. The description contributes two useful facts beyond that: reads are scoped to the main world, and the value comes back as a string. It does not disclose behavior for an unknown rule name (error vs. default), which is the main gap.

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?

A single short sentence with the resource, scope, and return type front-loaded and no wasted words. Nothing could be removed without losing information.

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?

For a trivial one-parameter read with full annotations, a complete input schema, and an output schema, the description covers what the agent needs to call it correctly. Only the unknown-rule error behavior is unstated, a minor omission for a tool of this simplicity.

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 schema already documents the 'rule' parameter with examples and legacy-name tolerance, so the description adds no parameter meaning. Baseline 3 is appropriate for a fully documented single parameter.

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?

Identifies the resource (a game rule) and the scope (main world) plus the return shape (string), so an agent knows it reads one rule's current value. It lacks an explicit verb like 'get' and doesn't name set_gamerule as the write counterpart, but the get/set naming pair makes the distinction inferable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use or when-not-to-use guidance; the description never mentions set_gamerule or any alternative. An agent must infer from the name alone that this is the read path and that mutation belongs elsewhere.

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