Skip to main content
Glama
lucasr1b

sketchdex

by lucasr1b
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

render_scene

Render a sketch scene to PNG to check proportions, overlaps, and readability. Writes a file and supports tiled or region views for close inspection.

Instructions

A PNG of the scene as it actually renders, so you can look at what you drew. Use it to check your own work - proportions, overlaps, whether the thing reads as the thing. Always written to a file as well as returned. A tall or wide page (long edge more than about twice the short one, and too big to fit at the asked size) comes back as a few tiles cut along its length, each with the scene box it shows, so a whole board is readable in one call; a region renders just that box, which is the way to look closely at one part. When an image is too big to travel inline you get a downscaled preview plus the file path.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsNoRender only these elements.
scaleNoPixel density, 1-3. Default 1.
sceneYesScene id, exact name, or a unique part of the name. Use list_scenes if unsure.
tilesNoSplit the picture into this many tiles along its long axis (max 8). Default: chosen from the shape of the scene, 1 for anything roughly square. Pass 1 to force a single image.
regionNoRender only what overlaps this box, in scene coordinates. Take the numbers from describe_scene's `bounds`.
maxWidthNoCap the long edge in pixels. Default 1400. Above ~1200 the result is a file path instead of an inline image.
transparentNoLeave the paper out of the PNG (alpha background). For dropping a sketch onto a slide or a page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden, and it discloses substantial behavior: output is always written to a file as well as returned, tall/wide pages are auto-tiled along the long axis with scene boxes, and oversized images degrade to a downscaled preview plus file path. It omits cost/latency and any error or permission behavior, so not quite exhaustive.

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?

Front-loads the core purpose in the first sentence, then layers on output/behavior details. It is somewhat dense and chatty with parenthetical asides, but every sentence conveys actionable information about output shape, so nothing is truly wasted.

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?

With 7 parameters, a nested object, no output schema, and no annotations, the description does the heavy lifting on return behavior (inline image vs. file path, tiling, preview downscale), which compensates for the missing output schema. Gaps remain around failure modes and permission/precondition behavior, but for a read-only render tool the coverage is strong.

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 coverage is 100%, so baseline is 3, but the description adds genuine meaning beyond the schema by explaining why `tiles` exists (long pages split for readability) and the practical consequence of `maxWidth` (above ~1200 you get a path instead of an inline image). It also frames `region` as the close-up mechanism rather than just a bounding box.

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 concrete verb+resource ('A PNG of the scene as it actually renders') and immediately frames the intent ('so you can look at what you drew'), which separates it from sibling validation/inspection tools like check_scene or describe_scene. An agent knows this is the visual-render tool, not a text or validation tool.

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?

Gives clear usage context ('Use it to check your own work - proportions, overlaps, whether the thing reads as the thing') and steers to `region` for close inspection. It does not explicitly name or exclude sibling alternatives (check_scene, snapshot_scene), so this falls just short of the top bar.

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