Skip to main content
Glama
Sign In
Blender MCP Ultra

Blender MCP Ultra

by 3bdull4h2008
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

configure_render

Configure Blender's render engine, device, samples, denoising, max bounces, and resolution to match exact output requirements.

Instructions

Configure render engine, GPU, samples, resolution, etc.

Args: engine: Render engine (CYCLES, BLENDER_EEVEE, BLENDER_WORKBENCH). samples: Number of samples for Cycles. device: "GPU" or "CPU" for Cycles device. denoising: Enable/disable denoising. max_bounces: Max light bounces for Cycles. resolution_x: Output width. resolution_y: Output height.

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": "configure_render"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNo
engineNo
samplesNo
denoisingNo
max_bouncesNo
resolution_xNo
resolution_yNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the responsibility for behavioral disclosure. It clearly communicates that this tool configures render settings and enumerates the affected fields, but it does not mention side effects like whether a render is triggered, whether previous settings are overwritten, or how engine-specific parameters are ignored.

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?

The one-sentence summary is front-loaded and the Args list is compact and scannable. Every line adds value, and there is no redundant prose.

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?

For a configuration tool with 7 optional parameters, no annotations, and no output schema, the description is largely self-contained and sufficient for invoking the tool correctly. It is only missing a short usage hint about when to apply these settings and how zero or default values are interpreted.

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 parameter descriptions are essential. The description compensates by explaining every parameter, including enum-like values for engine, explicit values for device, and meanings for samples, denoising, max_bounces, and resolution dimensions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action: 'Configure render engine, GPU, samples, resolution' and backs it up with a complete parameter list. It clearly identifies this as a render-settings tool, though it does not explicitly differentiate itself from render_preview, render_image, or set_viewport_shading.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is given about when to use this tool versus its render-related siblings. There is no mention of calling this before rendering, nor any indication of which settings apply to which engine beyond the parameter descriptions.

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