craftpilot-mcp

Overview Schema Source Related Servers Discussions Admin

mc_screenshot

Capture the Minecraft window as an image, downscaled to a maximum width, so AI assistants can inspect the game visually.

Instructions

Take a screenshot of the Minecraft window (returned as an image). Downscaled to maxWidth.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "mc_screenshot"
  }
}

Input Schema

Name	Required	Description	Default
`maxWidth`	No	Max image width in pixels (default 1280)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 7, 2026

TDQS

B3.3/5.0

Behavior3/5

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

With no annotations supplied, the description does some work by disclosing the output type (an image) and the downscaling behavior tied to maxWidth. It is silent on whether the call is read-only, whether it requires the window to be focused, latency, or how multiple displays/windows are handled.

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 short sentences, front-loaded with the action and followed by the caveat about downscaling. No filler and nothing that could be cut without losing information.

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?

For a single-optional-parameter read tool with no output schema, saying the result is an image is sufficient on the return-value side. However, the absence of any disambiguation from mc_screen leaves a real gap for an agent choosing a tool.

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 description coverage is 100%, so maxWidth, its default of 1280, and its bounds are already documented. The description only echoes the downscaling intent, adding no format or trade-off detail beyond the schema – baseline 3 applies.

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?

Names a specific verb and resource ("Take a screenshot of the Minecraft window") and adds the return form ("returned as an image"). It does not distinguish itself from the nearby sibling mc_screen, which an agent could reasonably confuse with it, so it falls short of a 5.

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?

There is no when-to-use guidance, no mention of alternatives such as mc_screen or mc_status, and no statement of prerequisites. The agent must infer that this is for visually inspecting the game state.

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