Skip to main content
Glama
Sign In
Boarderless MCP Server

Boarderless MCP Server

by CrackenReleased
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Render Board in Blender

render_board_in_blender

Transform your board canvas into a 3D rendered PNG with Blender. Automatically builds the scene, aligns lighting and camera, and exports the final image.

Instructions

Generate a 3D studio render of the current canvas using Blender. Automatically captures the board snapshot, decodes base64 assets, builds a 3D scene with lighting/camera alignment, and exports a finished PNG image. Requires Blender to be installed and available on the system environment path.

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

Input Schema

NameRequiredDescriptionDefault
engineNoBlender render engine. BLENDER_EEVEE is fast; CYCLES is high-fidelity path tracing. Defaults to BLENDER_EEVEE.
filenameNoOptional output render filename (e.g. render.png). Saved to the active project workspace.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.28

TDQS

A3.8/5.0
Behavior3/5

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

The description adds process details (capture snapshot, decode assets, build scene, export PNG) and the requirement for Blender. However, annotations indicate readOnlyHint=false, suggesting potential modification, while the description implies read-only behavior ('captures' without mention of mutation). This mild contradiction reduces transparency.

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?

Two sentences with no waste. The first sentence states purpose, the second elaborates process and requirement. Front-loaded and efficient.

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 the low complexity (2 optional params, no output schema), the description covers the main purpose, process, and a key requirement (Blender). Missing details on output resolution and potential side effects, but adequate for a simple tool.

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

Parameters3/5

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

Schema coverage is 100% and description provides no additional meaning for the two parameters (engine, filename). Baseline 3 is appropriate since the schema is self-explanatory.

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 verb 'generate a 3D studio render' and the resource 'current canvas'. It distinguishes from sibling tools like export_board and export_board_file by specifying the use of Blender for 3D rendering.

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?

The description implies usage for 3D rendering of the canvas, but it does not explicitly state when to use this tool over siblings (e.g., export_board for flat exports). It mentions the Blender requirement but lacks when-not or alternative guidance.

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