Skip to main content
Glama
Sign In

MagicPixel

by art.magicpixel
OverviewDiscussionsAdmin

Generate directions

generate_directions

Generate other facings of an existing sprite (in-app Directions). source_direction is required — ask the user if it is not obvious. Defaults: density quality, targets = the other cardinals. State the assumptions you used. Only an off-center subject blocks (fix_preflight: true re-centers it); brush/size findings are advisory warnings (fix_preflight: "all" applies them). ~8 credits (HD).

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": {
      "asset_id": "<asset_id>",
      "source_direction": "<source_direction>"
    },
    "name": "generate_directions"
  }
}

Input Schema

NameRequiredDescriptionDefault
saveNoAppend finished artboards into the source library file (default true).
densityNomax (1 facing) | quality (~3 facings, default). Quantity is treated as quality.
asset_idYesSource library asset id (from list_assets). Must face source_direction.
artboard_idNoOptional artboard id from get_asset. Multi-artboard files need artboard_id or artboard_name to pick one sprite; omit for single-artboard assets.
color_policyNoPalette policy matching in-app ColorPolicyControl: "32"|"64"|"128"|"256" (max colors) or "none" (don't reduce). Default "128". Put palette caps here, not in the prompt.
artboard_nameNoOptional artboard name from get_asset (e.g. "rocks_crystal"). Alternative to artboard_id.
fix_preflightNotrue = re-center the subject for this run (the only blocking finding). "all" = also apply the advisory brush and artboard-resize fixes, which can change the output size. Default false. The saved library file is not changed.
source_directionYesWhich way the source sprite faces now (N/NE/E/SE/S/SW/W/NW). Required — ask the user if it is not clear from the image or context.
subject_categoryNoSubject framing (default character); infer from the sprite.
target_directionsNoFacings to generate. Capped by density (max=1, quality≈3). Default: the other cardinals. Source facing excluded.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4/5.0
Behavior5/5

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

Beyond the annotations (which only declare non-readonly, open-world, non-idempotent, non-destructive), it discloses the credit cost (~8 HD), which preflight findings block versus which are merely advisory, that fix_preflight 'all' can change output size, and that the saved library file is not modified. That is exactly the behavioral context an agent cannot get from structured fields.

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?

It is dense and front-loaded: purpose first, then the hard prerequisite, then defaults, then failure modes and cost. The telegraphic clause stacking (defaults, preflight, credits in successive fragments) costs a little readability but almost no words are wasted.

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 10-parameter generation tool with no output schema, the description covers inputs, failure modes, and cost well but says nothing about what comes back — asset ids, new artboards, or job handles. An agent must call it blind regarding the result shape and any polling requirement.

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%, so every parameter is already documented, and the description largely restates schema content (density quality default, target defaults, fix_preflight semantics). It adds the 'ask the user' rule for source_direction and the target/density cap relationship, but nothing about save, color_policy, or artboard selection beyond what the schema says.

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 opens with a specific verb and resource ('Generate other facings of an existing sprite') and scopes it to the Directions feature, so the agent knows exactly what will be produced. It never distinguishes itself from plausibly overlapping siblings such as generate_variants, so it stops 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 Guidelines4/5

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

It gives concrete operating guidance: source_direction is mandatory, ask the user when unclear, density defaults to quality with other cardinals as targets, and state assumptions. It does not say when to prefer a sibling tool over this one, so there is no explicit alternative routing.

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

All MagicPixel toolsInspect
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