Skip to main content
Glama

render

Queue a Cycles camera image job and return a job ID; retrieve the PNG with view_image after processing. GPU jobs require a GPU session.

Instructions

Queue a Cycles camera render. Requires a camera; GPU requires a GPU session.

Returns a job ID. On success view_image retrieves the PNG. The live session
serializes renders with edits. Render settings are restored after the job.

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": {
      "session_id": "<session_id>"
    },
    "name": "render"
  }
}

Input Schema

NameRequiredDescriptionDefault
frameNo
widthNo
deviceNoCPU
heightNo
samplesNo
session_idYes
timeout_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/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 does well: it discloses the async job model (returns a job ID), the GPU/session prerequisite, that renders serialize with edits in a live session, and that render settings are restored afterward. It omits failure/timeout behavior and what happens when the camera is missing, which would complete the picture.

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?

Five short sentences, front-loaded with the core action and prerequisite, then the return value and follow-up tool. No filler; every sentence adds usable information.

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?

There is no output schema, and the description covers the return value (job ID) and how to retrieve the result, which is the key missing piece an agent would need. For a 7-parameter render job it could say more about failure modes and parameter tuning, but the essential workflow is covered.

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

Parameters2/5

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

Schema description coverage is 0% across 7 parameters, so the description must compensate but largely doesn't: frame, width, height, samples, session_id, and timeout_seconds are never explained. Only the device choice is indirectly addressed via 'GPU requires a GPU session', and even the required 'camera' is a scene concept rather than a listed parameter.

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 opening sentence names a specific verb and resource ('Queue a Cycles camera render'), which is unambiguous and distinct from sibling operations like view_image or viewport_screenshot. The follow-up sentence about view_image retrieving the PNG further pins down its role as the async job-submission step.

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?

It states clear prerequisites ('Requires a camera; GPU requires a GPU session') and the follow-up path via view_image, giving an agent enough context to know when this tool applies. It stops short of explicit exclusions or naming alternatives such as viewport_screenshot for quick previews.

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