Skip to main content
Glama
HoldMyBeer-gg

blend-ai

by HoldMyBeer-gg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_scene_property

Set Blender scene properties such as frame range, current frame, FPS, unit system, or render engine to control animation and rendering.

Instructions

Set a scene property such as frame_start, frame_end, frame_current, fps, unit_system, or render_engine.

Args: property: The scene property to set. Must be one of: frame_start, frame_end, frame_current, frame_step, fps, unit_system, render_engine, use_gravity, gravity. value: The value to set the property to. Type depends on the property.

Returns: Confirmation dict with the property name and new value.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
valueYes
propertyYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.7.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / property / enum
      Added value: +[
+  "fps",
+  "frame_current",
+  "frame_end",
+  "frame_start",
+  "frame_step",
+  "gravity",
+  "render_engine",
+  "unit_system",
+  "use_gravity"
+]
  2. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It discloses that the operation is a setter and returns a confirmation dict with the property name and new value, but says nothing about permissions, side effects, reversibility, or how changing one property might affect others. This is minimal for a mutation tool.

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

Conciseness4/5

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

The description is well-structured with Args and Returns sections and is front-loaded with the core purpose. It is concise overall, though the first sentence duplicates some of the property list that appears again in the Args section, leading to slight 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?

An output schema exists, so the return value need not be explained further. However, the description fails to compensate for the lack of parameter descriptions and annotations: it provides no type mapping for values, no guidance on alternatives, and no behavioral context for a tool that can mutate multiple scene settings.

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. It lists the enum values for the property parameter (though the schema already defines them) and states that the value's type depends on the property, but it does not specify what type or range each property expects. This leaves the agent unable to reliably choose a valid value.

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?

The description states a specific verb 'Set' and resource 'scene property', with a list of example properties. It is clear what the tool does, but it does not distinguish itself from closely related siblings like set_frame_range, set_render_engine, or set_frame, which could be used for some of the same properties.

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?

No guidance is given on when to use this tool versus the more specific setters in the sibling list (e.g., set_frame_range, set_render_engine). The description implies usage only through the list of properties, but does not mention alternatives, exclusions, or prerequisites.

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