cloudcraft-mcp

export_blueprint_image

Destructive

Render a Cloudcraft blueprint to an image file on disk in PNG, SVG, PDF, or mxGraph format, saving it to the configured export directory.

Instructions

Render a Cloudcraft blueprint to an image file on disk.

Writes are restricted to CLOUDCRAFT_EXPORT_DIR (default: system temp directory). Set CLOUDCRAFT_EXPORT_DIR=/path/to/dir in the MCP server environment to allow saving under a different directory.

Args: blueprint_id: Blueprint UUID. format: One of png, svg, pdf, mxgraph. Default png. output_path: Absolute path to save to, must resolve under the export directory. Default: <export_dir>/cloudcraft_<uuid>.<ext>. scale: Optional PNG render scale (e.g. 1.0, 2.0). PNG only. transparent: PNG transparent background (bool). PNG only. overwrite: Set True to replace an existing file at output_path. Default False — existing files are preserved.

Returns: {"path": <saved_path>, "bytes": <size>, "format": <fmt>}

Input Schema

Name	Required	Default
`scale`	No
`format`	No	png
`overwrite`	No
`output_path`	No
`transparent`	No
`blueprint_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.1.8Oct 20, 2026

addedInput schema / properties / overwrite

Added value: +{
+  "default": false,
+  "title": "Overwrite",
+  "type": "boolean"
+}

First observedv0.1.0Apr 22, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations declare destructiveHint=true and openWorldHint=true; the description explains what that destruction actually means ('overwrite... Default False — existing files are preserved') and bounds the write scope to the export directory. It also documents the return shape, so the risk profile and side effects are fully transparent rather than left to inference.

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?

Purpose is front-loaded in the first line, followed by well-organized Args/Returns sections where each entry earns its place. Minor redundancy: the CLOUDCRAFT_EXPORT_DIR variable and its default are explained across two sentences when one would suffice.

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 6-parameter write tool with high destructive potential, the definition covers directory constraints, path resolution rules, all defaults, format-specific parameter applicability, overwrite safety, and the return payload. Nothing an agent needs to call this correctly is missing.

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 description coverage is 0%, so the description carries the full burden and does so: it enumerates all six parameters, gives the accepted format values (png, svg, pdf, mxgraph), states the default output path pattern, and flags that scale and transparent apply to PNG only. This is meaning the schema alone does not convey.

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 ('Render') and resource ('a Cloudcraft blueprint') with the output medium ('image file on disk'), which immediately separates it from siblings like get_blueprint, export_blueprint_budget, and create_blueprint. An agent knows exactly what this 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 write-restriction section gives clear operational context: writes are confined to CLOUDCRAFT_EXPORT_DIR, and the env var is named for redirecting them. It does not explicitly state when to prefer this over alternatives (e.g. vs export_blueprint_budget), but the purpose is unambiguous enough that selection is implied.

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

Deploy Server