Skip to main content
Glama
Ref2Blender MCP Server

Ref2Blender MCP Server

by evarynstudio

render_views

Render auto-framed orthographic and perspective views of a Blender model, returning one image per requested view and optionally targeting a single asset sub-collection.

Instructions

Render the model, auto-framed, and return one image per view.

front/back/left/right/top/bottom are orthographic (front = camera on -Y looking towards +Y; right = camera on +X). three_quarter is a perspective view from the front-right and above; three_quarter_back from the back-left and above. Only the Ref2Blender collection is shown. Pass asset to render a single asset sub-collection.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "views": "<views>"
    },
    "name": "render_views"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeNo
assetNo
viewsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does disclose meaningful behavior: rendering is auto-framed, output is one image per requested view, and only the Ref2Blender collection is visible. That last constraint is important and non-obvious. It stops short of stating the return medium (inline image data versus written files), whether renders persist or overwrite, and whether concurrent renders conflict, which keeps it below a 5.

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 core action is front-loaded in the first line, followed by necessary per-view geometry definitions. Every sentence carries information, though the view-by-view camera explanation is dense and could be tightened with a single parenthetical about axes.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description says only 'one image per view' without specifying format, dimensions, or whether images are returned inline or saved. The `size` parameter goes unexplained. For a render tool that agents must chain with export or check steps, this leaves the agent guessing about the return payload.

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 description coverage is 0% across 3 parameters, so the description must fill the gap. It defines `asset` (a single asset sub-collection) and explains the meaning of every `views` enum value, which is genuinely useful. It says nothing about `size` (default 768), so one parameter remains undocumented everywhere.

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?

States a specific verb and resource: 'Render the model, auto-framed, and return one image per view.' It also clarifies the scope of what is rendered (only the Ref2Blender collection, or a single `asset` sub-collection), which tells an agent what it will get. It does not distinguish itself from siblings like export_model or scene_summary, but its purpose is still unambiguous.

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?

It gives concrete usage detail for the required `views` argument by defining the camera geometry behind each option, and it explains that `asset` scopes the render to a sub-collection. However, it never says when to use this tool rather than export_model, check_model, or execute_blender_code, and it omits prerequisites such as whether the scene must be loaded or checked first.

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