Skip to main content
Glama
gchen19

AnkusDrive

by gchen19
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Render Photoreal Submit

render_photoreal_submit

Start a photorealistic render asynchronously and get a job ID immediately, then poll for the finished image—keeping your workflow responsive during long renders.

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
viewNoiso
partsNo
sceneNo
widthNo
deviceNo
handleNo
heightNo
qualityNo
materialNo
rendererNoauto
output_dirNo
appearancesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
-]
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Discloses the non-blocking asynchronous behavior, immediate return payload shape, polling requirement, terminal statuses, and the returned artifacts (PNG and blend_path for Blender). This is substantial behavioral context beyond the sparse annotations, with no contradiction.

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?

Four purposeful sentences: async behavior and return value first, usage guidance second, polling instructions third, and shared-argument reference last. No filler or repetition; every sentence earns its place.

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?

The core workflow is well covered: submit, poll, retrieve result, handle failure, and check render_capabilities. The only gap is that full parameter semantics are delegated to render_photoreal rather than being summarized here, which may be insufficient if that sibling's description is not equally detailed.

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%, so the description must compensate, but it only refers the agent to render_photoreal for 'same arguments' and mentions quality='final' as an example. The 12 parameters remain unexplained in this definition, making selection of valid values reliant on external tool documentation.

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?

Starts with a specific action and resource: 'Start a photorealistic render asynchronously; returns immediately with {job_id, status, renderer}' and explicitly contrasts with render_photoreal. This clearly distinguishes the submit variant from its synchronous sibling.

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 tells the agent when to use this tool instead of render_photoreal: long renders with quality='final', large images, or big assemblies, to keep the worker responsive. It also gives the follow-up workflow: poll render_job(job_id) until status is 'done' or 'failed'.

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