Skip to main content
Glama

set_modifier_property

Configure Blender modifier properties such as levels, count, or offset by specifying object, modifier, property, and value.

Instructions

Set a property on a modifier (e.g., levels, count, offset, angle).

Args: object_name: Name of the object. modifier_name: Name of the modifier. property: The modifier property to set (e.g., 'levels', 'count', 'width', 'segments', 'angle', 'offset', 'ratio', 'iterations', or an object setting such as 'target' or 'object'). value: The value to set. Object, collection, texture and image settings take the name of an existing one.

Returns: Confirmation dict with updated property.

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": {
      "object_name": "<object_name>",
      "modifier_name": "<modifier_name>",
      "property": "<property>",
      "value": "<value>"
    },
    "name": "set_modifier_property"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYes
propertyYes
object_nameYes
modifier_nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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 the full behavioral burden. It mentions a confirmation dict return, but says nothing about what happens with an invalid property name, whether the object must be active/selected, whether the change is undoable, or any error behavior for a mutating tool.

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?

Front-loaded one-line purpose followed by a tight Args list; the parameter restatements are short and the property examples earn their space by supplying the only enumeration available given the empty schema.

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

Completeness4/5

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

For a 4-required-parameter mutation tool with zero schema coverage and no annotations, the description covers what to pass and roughly what comes back. The main remaining gap is failure/prerequisite behavior, though the presence of an output schema means return values need less explanation.

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 description coverage is 0%, so the description must compensate, and it largely does: it enumerates plausible property strings (levels, count, width, segments, angle, offset, ratio, iterations, target, object) and explains that object/collection/texture/image values take the name of an existing datablock. It stops short of clarifying numeric type expectations (int vs float vs vector) for the value parameter.

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 (set) and resource (a property on a modifier) and names concrete examples of the properties involved. It is distinguishable from add_modifier/remove_modifier/apply_modifier, but it never states explicitly that the modifier must already exist or that it operates on an existing modifier stack entry.

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

Usage Guidelines3/5

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

Usage is implied: you tweak a modifier after it has been added. There is no explicit 'use this when...', no mention of add_modifier as the prerequisite path, and no guidance on when to use apply_modifier or remove_modifier instead. The property examples hint at the intended context but do not route the agent.

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