Skip to main content
Glama
Sign In
Powder Toy MCP

Powder Toy MCP

by alinflorin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

execute

Run commands against the running Powder Toy game to draw elements, control simulation playback, inspect state, and adjust settings; call read_instructions first for command syntax.

Instructions

pt execute: run a command against the running Powder Toy game. IMPORTANT: call read_instructions first; it documents every command and its syntax.

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": "execute"
  }
}

Input Schema

NameRequiredDescriptionDefault
commandYesCommand line, e.g. "draw line DUST 10 10 200 10"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.6

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It does not say whether commands mutate game state (the schema example 'draw line DUST ...' strongly implies mutation), whether commands are reversible, what errors look like, or what the call returns. Only the implicit requirement that the game be running is disclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with no waste; the purpose is front-loaded and the prerequisite is flagged with a clear emphasis marker. Nothing unnecessary is included.

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 opaque string parameter feeding a command executor with no annotations and no output schema, the definition is minimally sufficient only because it delegates semantics to read_instructions. It leaves the mutating/read-only nature and result behavior of the call entirely undisclosed.

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?

There is one parameter with 100% schema description coverage and an inline example, so meaning is already conveyed structurally. The description adds no syntax, format, or length details beyond redirecting the agent to read_instructions, which is the baseline expectation at full coverage.

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?

States a specific verb and resource: run a command against the running Powder Toy game, and implies the game must already be running. It is clearly distinct from the sibling read_instructions, though the domain of possible commands is left entirely to that sibling.

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 an explicit prerequisite ordering — call read_instructions first because it documents every command and its syntax. This is strong routing guidance, but it does not say when this tool should not be used or what happens if the game is not running.

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