Skip to main content
Glama

render_canvas

Render a system diagram as a PNG image from a YAML recipe string, with automatic layout and support for hierarchical or flat node structures.

Instructions

Render a canvas diagram from a YAML recipe string. Supports hierarchical format (networks/factories/machines/nodes) or a simplified format (flat list of nodes with inputs/outputs). Returns the path to the rendered PNG file.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scaleNoRender scale factor (default 2.0 for crisp, legible output)
filenameNoOutput filename (without extension). Default: auto-generated UUID.
organizeNoApply the hierarchical organize algorithm for automatic layout with proper breathing room. Organizes nodes within machines, machines within factories, factories within networks — each with appropriate spacing. Default: true.
orientationNoLayout direction: 'horizontal' (left→right, default) or 'vertical' (top→bottom tree). Applied at all hierarchy levels.horizontal
yaml_recipeYesYAML string defining the canvas. Simplified format example: title: My Diagram nodes: - id: start type: input content: 'Begin here' - id: process type: process content: 'Do work' inputs: [start] Node types: static, input, ai, source, output, decision, process, default Coordinates (x, y) are optional — auto-layout is applied if all are 0.
spacing_levelNoSpacing level for organize layout: 'node' (tight: 60h/110v), 'container' (medium: 150h/190v, default), 'network' (spacious: 190h/250v).container
Behavior4/5

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

Despite no annotations, the description transparently states the output (PNG file path) and mentions format support. It doesn't contradict any annotations, but could detail side effects like file saving behavior.

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?

The description is two sentences, front-loading the core action. It's concise and includes necessary details like format types and output. Slightly more structure could improve scannability.

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?

Given 6 parameters, 1 required, and full schema coverage, the description adequately covers purpose, input format, and output. Lacks error handling info but overall sufficient.

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%, but the description adds value with a concrete example of the simplified YAML format. It complements the schema without redundancy.

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?

The description clearly states the tool renders a canvas diagram from a YAML recipe and returns a PNG path, with specific mention of supported formats. This distinguishes it from siblings like create_canvas, get_template, and list_templates.

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 description implies usage when you have a YAML recipe and want an output image, but does not explicitly state when not to use or provide direct alternatives. Still clear enough for most scenarios.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jdlongmire/ThinxAI-Canvas-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server