Skip to main content
Glama

render_final

Render a higher-quality final still from Blender with custom sample count and output path, producing a refined image for review or delivery.

Instructions

Render a higher-quality still.

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

Input Schema

NameRequiredDescriptionDefault
samplesNo
output_pathNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2/5.0
Behavior1/5

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

Annotations are absent, so the description carries the full behavioral burden and delivers essentially nothing. It does not disclose that a high-quality render is likely long-running or blocking, whether it overwrites an existing file at output_path, whether the scene must be saved first, or whether the call returns immediately versus on completion.

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?

It is a single front-loaded sentence with no filler, which is structurally clean. The brevity, however, reflects under-specification rather than economy – there is no wasted word, but there is also almost no information.

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?

An output schema exists, so return values need not be explained. Everything else an agent needs for a no-annotation, optional-parameter render tool – runtime expectations, file overwrite behavior, parameter meaning – is missing, making the definition inadequate relative to the tool's role.

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

Parameters1/5

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

Both parameters (samples, output_path) have 0% schema description coverage, so the description must compensate and does not mention either one. The meaning of samples, its typical range, and the format/destination semantics of output_path are left completely undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a concrete verb and resource ("render ... still") and adds a quality qualifier, so it is more than a restatement of the name. But "higher-quality" is relative and undefined – it never states what it is higher quality than (presumably render_preview) or how the output differs from render_scene/render_animation. An agent can guess the gist but cannot confidently separate it from the render siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisite or timing hint, and no named alternative. With siblings like render_preview, render_scene and render_animation present, the one thing an agent needs is a rule for choosing among them, and the description supplies none.

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