Skip to main content
Glama

render

Start a Houdini ROP job, inspect its output and camera settings, or monitor progress and the output file on disk.

Instructions

Start a render, read its settings, or watch it run.

Use it for a final picture through a ROP node. For a fast look at the
viewport, use capture instead: it is much quicker.

mode:
    "start"    — render the ROP at `path`. `frame_range` is [start, end];
                 without it the node renders its own range. A render can
                 take a long time.
    "progress" — what the ROP reports about the render.
    "settings" — the output file, the camera, the resolution and the
                 renderer of the ROP.
    "create"   — make a ROP of `render_type` ("opengl", "karma", "mantra",
                 "ifd", …) named `name` under `parent_path`.
    "watch"    — count the husk and mantra processes on this machine, and
                 say whether the file at `output_path` is there and how big
                 it is. This mode does not need Houdini, so it also works
                 while Houdini is busy with the render.

Returns JSON. A render that writes no file, with no process running, has
failed: read the node with cook to see the error.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoOne of "start", "progress", "settings", "create", "watch".start
nameNocreate: the name of the new ROP.
pathNostart, progress, settings: the ROP node.
frame_rangeNostart: [start, end]. Without it the ROP renders its own range.
output_pathNowatch: the image file to look for on disk.
parent_pathNocreate: the network that gets the ROP./out
render_typeNocreate: the ROP kind, for example "opengl", "karma", "mantra" or "ifd".opengl

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed34 schema fields changedv0.7.3
    • removedInput schema / properties / frame_range / anyOf
      Removed value: -[
      -  {
      -    "items": {
      -      "type": "number"
      -    },
      -    "type": "array"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • removedInput schema / properties / frame_range / default
      Removed value: -null
    • addedInput schema / properties / frame_range / description
      Added value: +"start: [start, end]. Without it the ROP renders its own range."
    • addedInput schema / properties / frame_range / items
      Added value: +{
      +  "type": "number"
      +}
    • removedInput schema / properties / frame_range / title
      Removed value: -"Frame Range"
    • addedInput schema / properties / frame_range / type
      Added value: +"array"
    • removedInput schema / properties / mode / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / mode / description
      Added value: +"One of \"start\", \"progress\", \"settings\", \"create\", \"watch\"."
    • removedInput schema / properties / mode / title
      Removed value: -"Mode"
    • addedInput schema / properties / mode / type
      Added value: +"string"
    • removedInput schema / properties / name / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • removedInput schema / properties / name / default
      Removed value: -null
    • addedInput schema / properties / name / description
      Added value: +"create: the name of the new ROP."
    • removedInput schema / properties / name / title
      Removed value: -"Name"
    • addedInput schema / properties / name / type
      Added value: +"string"
    • removedInput schema / properties / output_path / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • removedInput schema / properties / output_path / default
      Removed value: -null
    • addedInput schema / properties / output_path / description
      Added value: +"watch: the image file to look for on disk."
    • removedInput schema / properties / output_path / title
      Removed value: -"Output Path"
    • addedInput schema / properties / output_path / type
      Added value: +"string"
    • removedInput schema / properties / parent_path / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / parent_path / description
      Added value: +"create: the network that gets the ROP."
    • removedInput schema / properties / parent_path / title
      Removed value: -"Parent Path"
    • addedInput schema / properties / parent_path / type
      Added value: +"string"
    • removedInput schema / properties / path / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • removedInput schema / properties / path / default
      Removed value: -null
    • addedInput schema / properties / path / description
      Added value: +"start, progress, settings: the ROP node."
    • removedInput schema / properties / path / title
      Removed value: -"Path"
    • addedInput schema / properties / path / type
      Added value: +"string"
    • removedInput schema / properties / render_type / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / render_type / description
      Added value: +"create: the ROP kind, for example \"opengl\", \"karma\", \"mantra\" or \"ifd\"."
    • removedInput schema / properties / render_type / title
      Removed value: -"Render Type"
    • addedInput schema / properties / render_type / type
      Added value: +"string"
    • removedInput schema / title
      Removed value: -"toolArguments"
  2. Addedv0.1.1

TDQS

A4.7/5.0
Behavior5/5

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

The description goes beyond the annotations by detailing each mode's behavior, such as that a render can take a long time, that 'watch' counts processes and checks file existence, and that it works even when Houdini is busy. It also explains failure conditions and how to debug. Annotations only provide generic hints, while the description adds substantial operational context.

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 description is well-structured, front-loaded with the main purpose, then details modes, returns, and error handling. It is concise and every sentence adds value.

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

Completeness5/5

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

Given the tool's complexity (7 parameters, multiple modes) and the presence of an output schema, the description provides all necessary context: mode behaviors, return format, failure diagnosis, and alternative tool. It is complete for an agent to use correctly.

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 coverage is 100%, so the schema already documents all parameters. The description adds some mode-specific context (e.g., what frame_range means, what output_path is for) but largely repeats what is in the schema descriptions. Baseline of 3 is appropriate.

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 description clearly states the tool starts, reads, or watches a render, and it explicitly differentiates itself from the sibling 'capture' by explaining that render is for a final picture through a ROP node, while capture is a faster viewport look. This distinguishes it from siblings.

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?

It gives explicit guidance on when to use this tool versus the alternative ('capture'), and it details the different modes and their purposes, including when to use 'watch' (for monitoring without Houdini). It also explains failure condition and how to diagnose it.

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