Skip to main content
Glama

export_png

Save the current frame or all frames as a horizontal sprite sheet to a PNG file, blending layers as Pixelorama displays them.

Instructions

Export the current frame, or all frames as a horizontal sprite sheet, to a PNG file. Layers are blended the same way Pixelorama shows them.

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": {
      "path": "<path>"
    },
    "name": "export_png"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesWhere to write the file, ending in .png
frameNoFrame index, from 0. Defaults to the current frame
scaleNo
all_framesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It usefully discloses that layers are flattened/composited as displayed and that multi-frame exports are laid out horizontally, but it says nothing about overwriting existing files, whether parent directories must exist, or what happens on failure. The layer-blending note is genuinely valuable context beyond any structured field.

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 tight sentences with zero filler, front-loading the primary action and mode options before the layer-blending note. Nothing extraneous and nothing buried.

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 file-writing tool with no annotations and no output schema, the definition covers the core semantics but omits return behavior (does it return the written path?), overwrite handling, and interaction rules between frame and all_frames. Adequate but with clear gaps for a mutation 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 coverage is 50%: path and frame are documented in the schema, while scale (1–64) and all_frames have no schema description. The description partially compensates by explaining the all_frames behavior, but the scale parameter is never mentioned anywhere, leaving its meaning and effect undocumented.

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: 'Export ... to a PNG file', with two distinct modes (current frame vs. all frames as a horizontal sprite sheet). This is clearly distinguishable from siblings like get_image or save_project. It doesn't explicitly name a sibling alternative, but the action 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 context is implied by the wording: choosing between frame and all_frames is described, and 'layers are blended the same way Pixelorama shows them' signals this is a flattened visual export rather than a project file. There is no explicit when-to-use vs. alternatives (e.g., get_image) or stated preconditions.

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