Skip to main content
Glama
gbatistuta0

AppFactory

by gbatistuta0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Design Export PNG

design_export_png
Idempotent

Rasterize Claude Design boards to PNG via local headless Chrome for icons and store layouts. Use the render_preview serve_url with target width, height, and scale.

Instructions

Rasterize a Claude Design board to PNG with local headless Chrome.

Use when: icon (B01-AppIcon 1024x1024 to design/icon.png) or store layout boards (440x956, scale 3). serve_url comes from claude-design render_preview and is used once. Returns: {ok, path, width, height}.

Input Schema

NameRequiredDescriptionDefault
scaleNoDevice scale factor (default 1; use 3 for store boards).
widthYesViewport width in CSS pixels, e.g. 1024 for the icon board or 440 for a store board.
heightYesViewport height in CSS pixels, e.g. 1024 for the icon board or 956 for a store board.
out_pathYesOutput file path (PNG).
serve_urlYesTemporary serve_url from claude-design render_preview; used once, never stored.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.1.5
    • addedInput schema / properties / height / description
      Added value: +"Viewport height in CSS pixels, e.g. 1024 for the icon board or 956 for a store board."
    • addedInput schema / properties / out_path / description
      Added value: +"Output file path (PNG)."
    • addedInput schema / properties / scale / description
      Added value: +"Device scale factor (default 1; use 3 for store boards)."
    • addedInput schema / properties / serve_url / description
      Added value: +"Temporary serve_url from claude-design render_preview; used once, never stored."
    • addedInput schema / properties / width / description
      Added value: +"Viewport width in CSS pixels, e.g. 1024 for the icon board or 440 for a store board."
  2. First observedv0.1.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare the safety profile (not read-only, idempotent, non-destructive, closed-world). The description adds meaningful context beyond them: it runs Chrome locally, serve_url is consumed exactly once and never stored, and it reports the output path and dimensions. It doesn't mention failure modes or overwrite behavior for an existing out_path.

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?

Three short, front-loaded blocks with no filler; purpose first, then usage, then the return shape. The 'Returns: {ok, path, width, height}' line is somewhat redundant given an output schema exists, but it costs little.

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 5-param rendering tool with full schema coverage, annotations, and an output schema, the description supplies the trigger scenarios and side-effect notes an agent needs. The only gap is that it does not say what happens if out_path already exists or when a render fails.

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 description coverage is 100%, so every parameter is already documented (including serve_url provenance and the scale=3 hint). The description mostly restates that same guidance rather than adding syntax, constraints, or edge cases, so the baseline 3 applies.

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 ('Rasterize a Claude Design board to PNG') plus the mechanism ('local headless Chrome'), which distinguishes it from screenshot_* and preview_* siblings. An agent can tell what it produces without opening the schema.

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?

The 'Use when' line gives concrete triggering cases with dimensions (icon B01-AppIcon 1024x1024, store boards 440x956 at scale 3), which is clear context. However, it never names an alternative tool or an exclusion condition, so routing versus other export/screenshot tools is left to inference.

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

Deploy Server

Other Tools