Skip to main content
Glama

Render a shot

raster_render

Renders a shot (a camera through the engine's world: forms from the sculptor, people and animals from the rig, open country, primitives, under the game's own sky, sun, shadow and haze) at t seconds as shot.png. width and height (both or neither) set the size, else the shot's own; at most 1920 by 1080 either way up. Costs 3 units plus 1 for each 1.6 megapixels: 4 at 1280x720, 5 at 1920x1080. A shot can draw a world of ours, named by id and never by a path (copperside and low-quarter): a zone subject {"kind": "zone", "world": "copperside", "zone": "city", "cut": [x, z, radius], "crowd": false} draws a street (copperside's start zone is city), and a terrain subject with the same world key draws its country. A street draws its crowd by default, which is most of its price: a still in a world costs 5 units more, one that draws the crowd 26.2 more again. It runs as a queued job: the answer is 202 with a job id at once, and GET /api/agents/jobs/ (or the MCP tool job) says when it is done and signs its files. A queued call is refused on the free plan with 402: its units buy only calls that answer at once, and queued jobs need the subscription.

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": {
      "shot": "<shot>"
    },
    "name": "raster_render"
  }
}

Input Schema

NameRequiredDescriptionDefault
tNoThe moment to draw, in seconds from the shot's start, for a shot with motion.
shotYesA shot document written inline: a camera, the sun and air, and subjects. raster_schema lists every key.
widthNoOutput width in pixels, 16 to 1920; overrides the shot's own.
heightNoOutput height in pixels, 16 to 1920; overrides the shot's own.

Output Schema

NameRequiredDescriptionDefault
msNoMilliseconds the run took.
jobYesThe job id; the job tool reads it.
verbNoThe tool that made it.
filesNoFiles made, each with a name, type, size and a signed URL.
unitsNoUnits this call cost.
resultNoThe engine's own answer, a JSON document.
statusNoqueued when the job runs in the background.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / height / description
      Added value: +"Output height in pixels, 16 to 1920; overrides the shot's own."
    • addedInput schema / properties / t / description
      Added value: +"The moment to draw, in seconds from the shot's start, for a shot with motion."
    • addedInput schema / properties / width / description
      Added value: +"Output width in pixels, 16 to 1920; overrides the shot's own."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": true,
      +  "properties": {
      +    "files": {
      +      "description": "Files made, each with a name, type, size and a signed URL.",
      +      "items": {
      +        "additionalProperties": {},
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "job": {
      +      "description": "The job id; the job tool reads it.",
      +      "type": "string"
      +    },
      +    "ms": {
      +      "description": "Milliseconds the run took.",
      +      "type": "number"
      +    },
      +    "result": {
      +      "description": "The engine's own answer, a JSON document."
      +    },
      +    "status": {
      +      "description": "queued when the job runs in the background.",
      +      "type": "string"
      +    },
      +    "units": {
      +      "description": "Units this call cost.",
      +      "type": "number"
      +    },
      +    "verb": {
      +      "description": "The tool that made it.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "job"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Goes far beyond the annotations, which only say this is a non-read-only, non-destructive call. It discloses the exact price formula with worked examples (4 units at 1280x720, 5 at 1920x1080), the surcharge for a world still and again for a crowd (5 and 26.2 units), the asynchronous 202-plus-job-id contract, and the free-plan 402 refusal — everything an agent needs to predict cost and failure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Nearly everything earns its place, but it arrives as one dense block with a long atmospheric parenthetical ('forms from the sculptor, people and animals from the rig...') and cost rules split across two locations. Front-loading is good; structure and scanning ease are not.

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?

For a paid, asynchronous, nested-object render call, the description covers cost, size constraints, subject addressing, job polling, and plan gating, and an output schema exists so return values need no explanation. Nothing an agent needs to invoke it correctly is missing.

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

Parameters4/5

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

Schema coverage is already 100%, so the baseline is 3, but the description adds real meaning: the both-or-neither coupling of width and height and the 1920x1080 total ceiling ('either way up'), which the schema's per-field maximums do not express. It also illustrates the otherwise-opaque shot object with a concrete zone subject example and points at raster_schema for the full key list.

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?

Opens with a specific verb and resource: renders a shot to shot.png at t seconds, and even defines what a shot is composed of (camera, subjects, sun, air). It never names a sibling such as video_render or art_render, so the agent must infer that this tool is the still-image path.

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?

Gives concrete usage conditions: width and height must be supplied both or neither, shots must reference worlds by id and never by a path, and queued calls are refused on the free plan with 402. It also routes polling to GET /api/agents/jobs/<job> or the MCP job tool, though it offers no explicit when-not-to-use against the render siblings.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources