Skip to main content
Glama

pixoo_compose_scene

pixoo_compose_scene
Idempotent

Compose layered scenes with text, icons, widgets, shapes, images, and sprites. Add per-element effects and keyframe animations, render back-to-front, and preview as an image before pushing to your Pixoo display.

Instructions

Compose a full scene: layered elements (text, icons, widgets, shapes, bitmaps, images, sprites) with per-element effects and keyframes, static or animated. Returns the rendered scene as an image content block for immediate inspection. Elements render back-to-front in array order. For text-only display use pixoo_display_text; run pixoo_design_brief with topic "scene" or "dashboard" for layout and palette guidance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
backgroundYesScene background: solid color, gradient, or named theme.
elementsYesScene elements rendered back-to-front. Up to 50 elements.
framesNoNumber of animation frames (1–40, default: 1). 20 frames at 150ms ≈ 3s loop.
speedNoMilliseconds per frame for animations (default: 150ms).
pushNoPush to device (default: true).
outputNoExplicit output file path for saving (overrides PIXOO_OUTPUT_DIR).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pushedYesTrue when the device acknowledged the push. False when push: false or push failed.
previewDataNoBase64-encoded PNG preview of the rendered scene (8× upscaled, 512px). For animations: the middle frame.
previewMimeTypeNoMIME type of the preview image.
framesYesNumber of frames in the rendered output (1 for static, 2–40 for animations).
layoutYesLayout report for each element.
deviceStateNoDevice state after the push. Absent when push: false.
outputFilesNoAbsolute paths to saved output files (PNG for static, GIF for animations). Present only when PIXOO_OUTPUT_DIR is configured or output is set.
noticeNoWarning or informational notice about the render or push.
Behavior4/5

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

Annotations indicate read-only, idempotent behavior. Description adds rendering order ('back-to-front in array order') and return value ('image content block'), complementing annotations without contradiction.

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?

Three sentences with no wasted words. Front-loaded with the main action. Every sentence earns its place by explaining functionality, return value, and alternatives.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (multiple element types, effects, animation), the description covers key aspects: layering, animations, return value, and sibling differentiation. The presence of a complete output schema reduces the burden on the description.

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?

The input schema has 100% description coverage for all parameters, so the description adds no additional parameter details beyond what the schema provides. Baseline 3 is appropriate.

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?

The description clearly states the verb 'compose' and resource 'full scene' with specific element types. It distinguishes from the sibling pixoo_display_text for text-only display, ensuring the agent selects the correct tool.

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

Usage Guidelines5/5

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

Explicitly provides when-to-use guidance: 'For text-only display use pixoo_display_text' and recommends pixoo_design_brief for layout/palette help. This helps the agent choose between tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/cyanheads/pixoo-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server