SpriteForge Editor

Open a sprite in the SpriteForge editor

open_editor

Opens pixel art in SpriteForge's compact pixel editor - pencil, eraser, fill, colour picker, palette, undo and animation frames - as an interactive card where the app shows them, and returns an edit link (the same editor in a browser) and a session_id. No account needed. One source at most: png_base64 (an existing PNG), art (palette + index grid), or neither for a blank width x height canvas. Max 128x128 pixels and 256 colours. The user's edits save to the edit session automatically.

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

Input Schema

Name	Required	Description
`art`	No	Pixel art in SpriteForge's format: palette = hex colours, grid = rows of palette indexes (-1 = transparent). Optional frames for an animation, each { grid } on the same palette.
`name`	No	Sprite name, used as the download filename (letters, digits, _ and -).
`width`	No	Blank canvas width in pixels (default 32).
`height`	No	Blank canvas height in pixels (default 32).
`palette`	No	Starting palette for a blank canvas, as hex colours.
`png_base64`	No	A PNG file, base64-encoded (a data: URL prefix is fine). Pixels under 50% alpha become transparent.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A4/5.0

Behavior5/5

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

Annotations only declare that this is not read-only, not idempotent, not open-world and not destructive. The description adds substantial context beyond that: it returns an edit link and session_id, renders as an interactive card, requires no account, auto-saves edits, and enforces size/colour limits.

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?

The description is front-loaded with the core action and return behavior, and every sentence contributes practical information. It is somewhat dense and packs multiple constraints into a short span, but there is little outright waste.

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 six-parameter, nested-input tool with no output schema, the description is largely complete: it explains return values, input source options, limits, and save behavior. It could say more about session_id lifecycle or how the edit link is used later, but the essential invocation context is present.

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?

Schema description coverage is already 100%, so the schema carries the detailed parameter documentation. The description still adds meaningful semantics by stating the mutually exclusive source rule ('One source at most') and summarizing png_base64 vs art vs blank canvas, which is not fully expressed in the schema itself.

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?

The description clearly states a specific verb and resource ('Opens pixel art in SpriteForge's compact pixel editor') and scopes the format (128x128, 256 colours). It implies differentiation from the full/tileset editors via 'compact pixel editor', but does not explicitly name those sibling tools, so it falls short of full sibling differentiation.

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?

The description gives useful input-selection guidance ('One source at most: png_base64, art, or neither for a blank width x height canvas') and notes no account is needed. However, it never explains when to use this tool versus open_full_editor or open_tileset_editor, leaving the primary alternative-selection question to inference.

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

All SpriteForge Editor tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?