Skip to main content
Glama
Sign In
minecraft-mcp

minecraft-mcp

by IotA-asce
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Toggle sprinting

sprint

Toggles fast movement for a Minecraft player. Enable or disable running mode for an online player to alter their movement speed.

Instructions

Enable or disable sprinting for the player.

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": {
      "enabled": "<enabled>"
    },
    "name": "sprint"
  }
}

Input Schema

NameRequiredDescriptionDefault
playerNoOnline player name (defaults to the first online player)
enabledYestrue to start sprinting, false to stop

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It states the core behavior (enable/disable sprinting) but adds no extra context about side effects, prerequisites (e.g., player online), or persistence. It is minimally adequate for a simple toggle, but does not go beyond a restatement of the schema.

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?

The description is a single, concise sentence that immediately conveys the tool's purpose. It is front-loaded and contains no extraneous 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 simple 2-parameter tool with no output schema, the description adequately covers the essential behavior. The schema fills in parameter details, and the description is sufficient to understand the tool's function, though it lacks deeper context about when to use it.

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%, with the description of 'enabled' already explaining true/false semantics. The tool description adds no additional parameter meaning beyond the schema, so it meets the baseline but does not exceed it.

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 clearly states 'Enable or disable sprinting for the player' with a specific verb (enable/disable) and resource (sprinting). It distinguishes from siblings like 'sneak' and 'stop' by clearly referring to the sprint action.

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 guidance is provided on when to use this tool versus alternatives. The description simply states what it does without mentioning exclusions or other tools like 'sneak' or 'stop', leaving usage context entirely to the reader.

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

Deploy Server

Other Tools