Skip to main content
Glama

Render Photoreal Submit

render_photoreal_submit

Start a photorealistic render asynchronously and return a job ID immediately; poll render_job until done, so long final-quality renders do not block the worker.

Instructions

Start a photorealistic render asynchronously; returns immediately with {job_id, status, renderer} instead of blocking for the whole render.

Use this (rather than render_photoreal) for renders that may take a long time — quality='final', large images, big assemblies — so the worker stays responsive. Poll render_job(job_id) until status is 'done' (then it returns the PNG and, for Blender, blend_path) or 'failed'. Same arguments, renderer selection and not-installed miss dict as render_photoreal; see render_capabilities for what resolves on this machine.

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

Input Schema

NameRequiredDescriptionDefault
viewNoiso
partsNo
sceneNo
widthNo
deviceNo
handleNo
heightNo
qualityNo
materialNo
rendererNoauto
workspaceNoRun this call in this named workspace
output_dirNo
appearancesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • addedInput schema / properties / workspace
      Added value: +{
      +  "default": "",
      +  "description": "Run this call in this named workspace",
      +  "title": "Workspace",
      +  "type": "string"
      +}
  2. Changed11 schema fields changedv0.5.5
    • addedInput schema / properties / appearances
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": true,
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Appearances"
      +}
    • addedInput schema / properties / device
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Device"
      +}
    • addedInput schema / properties / handle / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / handle / default
      Added value: +null
    • removedInput schema / properties / handle / type
      Removed value: -"string"
    • addedInput schema / properties / output_dir
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Output Dir"
      +}
    • addedInput schema / properties / parts
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "additionalProperties": true,
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Parts"
      +}
    • addedInput schema / properties / quality
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Quality"
      +}
    • changedInput schema / properties / renderer / default
      Previous value: -"Povray"New value: +"auto"
    • addedInput schema / properties / scene
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Scene"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "handle"
      -]
  3. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations cover only the safety profile (non-readonly, non-destructive, closed-world), so the description adds the substantive behavior itself: non-blocking execution, the immediate return payload keys, both terminal states and what they yield (PNG, and blend_path for Blender), and the 'not-installed miss dict' error shape shared with render_photoreal. That is exactly the async-contract context an agent cannot get from the annotations.

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?

Three tight sentences: what it does, when to pick it over the sibling, then the polling contract. The one weakness is that the alternative/polling guidance is wrapped inside the 'start' sentence block, slightly diluting front-loading of the async return shape.

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?

For an async submit tool with no output schema, the description does disclose the return keys and the polling path to completion, which is the critical piece. But with 13 parameters at 8% coverage and required=0, an agent still cannot tell which knobs matter or what defaults mean, leaving a real gap for a tool of this complexity.

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 only 8% across 13 parameters, so the description carries the burden but mostly defers ('Same arguments, renderer selection ... as render_photoreal'), pushing the agent to another tool's schema. Only quality='final' is given as a concrete value hint; view, scene, parts, material, appearances, device, handle and output_dir remain unexplained anywhere.

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 specific verb and resource ('start a photorealistic render asynchronously') with the key differentiator baked in: it returns immediately with {job_id, status, renderer} rather than blocking. An agent can distinguish it from the sibling render_photoreal without opening either schema.

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 names the alternative ('Use this rather than render_photoreal') and the conditions that select it: quality='final', large images, big assemblies, long renders. It also closes the loop with the follow-up call pattern ('Poll render_job(job_id) until status is done or failed'), leaving nothing to inference.

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