Skip to main content
Glama
pixelorama-mcp
by Aeroscoop

set_color_mode

Switch a Pixelorama project between indexed and RGBA color modes to support palette-based pixel editing or full-color work, with the change recorded as one undo step.

Instructions

Switch the project between 'indexed' (every pixel is a palette slot) and 'rgba'. One undo step.

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": {
      "mode": "<mode>"
    },
    "name": "set_color_mode"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/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 behavioral burden and does add value by disclosing that the operation is a single undo step (i.e., reversible). However it omits key behaviors for a project-wide conversion: what happens to existing pixel colors when switching to indexed, and whether a palette must already exist.

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, zero padding, with the mode semantics and the undo consequence front-loaded and immediately usable.

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 simple one-parameter tool with no output schema this is nearly sufficient, but a project-wide image transformation should mention the irreversible-looking consequences of converting to indexed (color quantization, palette dependency), which are currently left unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema enum lists 'indexed' and 'rgba' but provides no descriptions (0% coverage); the description compensates by explaining that 'indexed' means every pixel is a palette slot, which is the one piece of semantics an agent actually needs to choose the value.

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 ('Switch the project between indexed... and rgba') and defines what each mode means, so an agent knows exactly what the tool does. No sibling in the list touches color mode, so the scope is unambiguous.

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

Usage Guidelines3/5

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

Usage is only implied: the parenthetical explanations of 'indexed' and 'rgba' suggest when each mode is appropriate, but there is no explicit when-to-use/when-not guidance, no note that a palette is required for indexed mode, and no prerequisites stated.

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