Skip to main content
Glama
asedias

bl-mcp

by asedias
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

render_final

Render the final presentation image from the scene camera, lights, and materials to a file; set a camera first or pass one for the shot.

Instructions

The presentation picture: render through the scene camera with the scene lights and materials to a file. Needs a camera: call set_camera first (or pass camera). For check pictures use render_sheet (overview) or render_view (any angle), they need no set-up. path is absolute, or relative to the work folder; the folder is created. engine: eevee (fast), cycles (slow, CPU, real light), workbench (flat preview, no lights needed). size is pixels for a square, or [width, height]. samples is the quality: 16-64 for eevee, 32-256 for cycles. transparent writes alpha (PNG, WEBP, TIFF, OPEN_EXR) and hides the world. denoise is for cycles only. view_transform: Standard keeps colours true; Filmic, AgX or Khronos PBR Neutral if the Blender build has them. exposure is in stops for this render only (+1 doubles the light); without it the scene exposure (set_post) is used. auto_exposure=true first renders a small probe and picks the exposure that puts the median luminance of the geometry at mid grey; the answer has auto_exposure. meter is a list of object names (with children) to measure instead of all geometry: give the model, so a floor or backdrop does not steer the exposure. Except for OPEN_EXR the answer has tone numbers of the written picture (0-1): frame and, when the geometry is known (meter, auto_exposure or transparent), object: median, mean, clipped_highlights and crushed_blacks. warnings appears when over 10% is clipped or over 50% is black. Read these numbers before you trust the picture. The scene settings are restored afterwards.

Input Schema

NameRequiredDescriptionDefault
pathYes
sizeNo
meterNo
cameraNo
engineNoeevee
denoiseNo
samplesNo
exposureNo
file_formatNoPNG
transparentNo
auto_exposureNo
view_transformNoStandard

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only declare readOnly=false, destructive=false, openWorld=false; the description adds substantial context beyond that – the folder is created, scene settings are restored afterwards, exposure is per-render, auto_exposure runs a probe pass, and the return carries tone numbers plus warnings at clipping/black thresholds.

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?

Dense but front-loaded: the camera requirement and sibling routing come first, then parameter semantics, then return values. Given 12 parameters at 0% schema coverage the length is largely earned, though a few clauses could be tightened.

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?

With no output schema and 12 undocumented parameters, the description supplies prerequisites, side effects, per-parameter meaning, and the shape of the response (tone statistics, warnings). Nothing an agent needs to call it correctly appears 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 must carry the burden and it does: it explains path resolution and folder creation, engine trade-offs, size as square vs [width,height], samples ranges per engine, transparent's format and world-hiding behavior, denoise being cycles-only, view_transform options, exposure in stops, auto_exposure, and meter semantics.

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 precise verb and resource: 'render through the scene camera with the scene lights and materials to a file.' It also distinguishes itself from siblings by naming render_sheet and render_view and describing how they differ (no set-up required).

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?

Explicitly gives prerequisites ('Needs a camera: call set_camera first (or pass camera)') and routes the agent to alternatives for check pictures. The condition selecting each sibling is stated, not inferred.

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