Skip to main content
Glama

render_result

Queue rendering of an existing computed simulation trajectory by run ID, with optional layers and options, without rerunning physics or supplying commands.

Instructions

Queue rendering of an existing computed trajectory. No commands, paths or physics reruns accepted.

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": {
      "run_id": "<run_id>"
    },
    "name": "render_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
layersNo
run_idYes
optionsNo
profileNopreview
idempotency_keyNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.1

TDQS

B3.4/5.0
Behavior3/5

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

No annotations exist, so the description carries the burden, and it does disclose meaningful traits: this is an asynchronous queued job rather than a synchronous render, and it operates on prior state rather than re-running physics. It says nothing about cost, permissions, failure behavior, or the purpose of idempotency, which are relevant for a mutation that queues work.

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?

Two sentences, front-loaded with the action and scoped by the constraint clause. No filler, no restatement of the tool name, no redundancy.

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

Completeness2/5

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

For a five-parameter mutation with no annotations and an output schema, the definition leaves the agent guessing about layers selection, the profile quality presets, the shape of options, and when to supply an idempotency key. The output schema covers return values, but the input-side gaps are material to calling this correctly.

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 five parameters, so the description must compensate and largely does not. Only run_id gains implicit meaning (a reference to an existing run, not a path); layers, options, profile (defaulting to 'preview'), and idempotency_key are left entirely unexplained in both places.

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?

States a specific verb and resource: 'Queue rendering of an existing computed trajectory.' That reads as distinct from compute-oriented siblings like run_scenario and from retrieval siblings like get_render_job. It stops short of naming any sibling, so differentiation is inferred rather than stated.

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?

The prerequisite is clear ('an existing computed trajectory') and the exclusions are explicit ('No commands, paths or physics reruns accepted'), which tells the agent not to use this as a compute entry point. It does not point to the alternative tools for computing a trajectory or for polling the queued job, so routing is only partly covered.

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