Skip to main content
Glama

Run a console command

run_command
Destructive

Execute any Minecraft command as the server console to perform operator-level actions beyond the per-call block limit. Only command dispatch status is reported, not output.

Instructions

Run any Minecraft command as the server console.

Unrestricted escape hatch: it can do anything an operator can, including stopping the server, and the per-call block limit does not apply. Prefer the dedicated tools. The plugin only reports whether the command was dispatched; the command's output is not returned.

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": {
      "command": "<command>"
    },
    "name": "run_command"
  }
}

Input Schema

NameRequiredDescriptionDefault
commandYesOne command line, with or without the leading '/', e.g. 'weather clear' or '/say hi'.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare destructive=true and non-idempotent, but the description adds crucial context they cannot carry: the tool can stop the server, the per-call block limit is bypassed, and the plugin only reports dispatch rather than command output. The last point prevents an agent from falsely assuming it can read results.

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?

Four short sentences, zero redundancy: capability, risk, preferred alternative, and return-value caveat all front-loaded in that order. Nothing can be removed without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Although an output schema exists, the description supplies the one thing the schema cannot communicate — that the response indicates dispatch only, not output — alongside the escalation and destructiveness risks. Nothing needed to invoke it safely is missing.

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 single 'command' parameter, including the optional leading slash and example. The description contributes only the side note that the block limit does not apply, so the schema still does the heavy lifting — baseline 3.

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?

States a specific verb and resource ('Run any Minecraft command as the server console') and immediately frames it as an 'Unrestricted escape hatch', which tells an agent exactly what class of tool this is relative to the dedicated siblings.

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

Usage Guidelines4/5

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

Gives explicit routing guidance — 'Prefer the dedicated tools' — which is the when-not rule an agent needs. It stops short of naming a specific sibling or spelling out the narrow escalation conditions that justify using this tool instead, so it is strong but not fully explicit.

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