Skip to main content
Glama

render_preview

Render a Wonderdraft map to a PNG preview for visual inspection, with optional bounding-box zoom, scale control, and object ID tagging; the output includes the saved file path.

Instructions

Render the map to a PNG you can see (also saved to disk; the path is in the text). scale is output px per map px (the output is capped at 8192 px on its longest side). bbox [x0, y0, x1, y1] in map pixels zooms in; show_ids tags objects with their ids.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "render_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
bboxNo
scaleNo
show_idsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does reasonably well: it discloses the disk side effect, where the path appears, and the 8192 px output cap. It leaves unstated whether the render reflects unsaved map state and whether repeated calls overwrite the same file.

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?

A single tight paragraph with the primary outcome front-loaded and the three parameter clarifications in parentheses. Every clause conveys information an agent could not get elsewhere.

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?

No output schema and no annotations, so the description covers the essentials: the artifact produced, its cap, disk persistence, path reporting, and all parameter meanings. Minor gaps are the default scale value and whether the render targets the currently open map or a specified one.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must explain all three parameters, and it does: scale is defined as output px per map px, bbox is given a format and an effect ('zooms in'), and show_ids is defined as tagging objects with ids. This is meaningful compensation for a completely undocumented schema.

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 concrete verb and resource ('Render the map to a PNG') plus the useful fact that the image is also written to disk with the path reported in the text. It does not explicitly distinguish itself from the sibling export_image, so an agent must infer which raster-producing tool to pick.

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 is implied ('a PNG you can see' suggests quick visual preview) and the bbox parameter implies zooming into a sub-area, but there is no explicit when-to-use guidance and no named alternative or exclusion relative to export_image.

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