Skip to main content
Glama

export_image

Exports the open Wonderdraft map as a PNG or JPG file at a specified path without overwriting existing files, either through the Wonderdraft app or a full-scale preview render.

Instructions

Export the open map as an image file at path (never overwrites an existing file; a .png/.jpg suffix must match format, and is added if missing). via="wonderdraft" drives the real Wonderdraft app (Windows only) and takes about 15-20 s: close Wonderdraft first and do not type meanwhile. It needs the map saved with no unsaved edits. If automation is unavailable or fails, nothing is written and the result has via="instructions" with manual steps (open the map, press Ctrl+E) in the summary. via="preview" writes a full-scale render from this server instead.

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_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
viaNowonderdraft
pathYes
formatNopng

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full behavioral burden and does so: no-overwrite guarantee, suffix/format coupling, Windows-only platform constraint, duration, concurrency warning, and the failure contract (nothing is written; result carries via="instructions" with manual Ctrl+E steps). These are exactly the traits an agent cannot infer from schema or annotations.

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-loaded with the action and path rules, then mode behavior; nearly every clause carries information. It is dense and parenthetical-heavy, and the sentence wrapping around "via=wonderdraft" makes it slightly harder to scan than it needs to be.

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?

For a 3-parameter mutation-with-side-effects tool with no output schema, the definition covers preconditions, failure mode, timing, and the shape of a degraded result. The only minor omission is what a successful result contains beyond the file being written.

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 0%, so the description must compensate, and it largely does: path semantics (never overwrites, suffix must match format, suffix auto-added) and both via enum values are explained with consequences. Format is only addressed indirectly through the .png/.jpg suffix rule rather than as a named parameter.

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 up front: "Export the open map as an image file at path." It also distinguishes the two execution modes (real Wonderdraft app vs. server-side render), which is the key ambiguity an agent would otherwise face with render_preview as a sibling.

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?

Gives explicit selection criteria per mode: via="wonderdraft" drives the real app (Windows only, ~15-20s, requires a saved map with no unsaved edits), while via="preview" renders from the server. Prerequisites (close Wonderdraft, don't type meanwhile) and a fallback path are spelled out.

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