Skip to main content
Glama

modify_object

Adjust a named Blender object's location, rotation, scale, or dimensions to update scene geometry.

Instructions

Modify common object properties.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
scaleNo
locationNo
rotationNo
dimensionsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2/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, and it says essentially nothing. It does not state that this is an overwriting mutation of an existing object, whether omitted parameters are preserved, whether values are in radians or degrees, or what happens if the named object does not exist.

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 short sentence with no wasted words, which is structurally clean, but the brevity comes from under-specification rather than discipline. There is no front-loaded detail an agent could act on.

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, but for a mutation tool with no annotations and five undocumented parameters the description is far too thin. It should at minimum enumerate which properties are modifiable and clarify its relationship to the transform/scale/rotate siblings.

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?

Schema description coverage is 0% for five parameters, so the description must compensate and does not. It never mentions 'name', 'scale', 'location', 'rotation', or 'dimensions', and gives no hint about the expected array shapes (2D vs 3D) or unit conventions for the vector fields.

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

Purpose2/5

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

The description restates the tool name ('modify' an 'object') and adds only the vague qualifier 'common properties'. It never names the actual modifiable fields (scale, location, rotation, dimensions) nor distinguishes this tool from siblings like set_object_transform, scale_object, rotate_object, or move_object, so an agent cannot tell which one to pick.

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 or when-not-to-use guidance at all. Given the crowded sibling set that clearly overlaps (set_object_transform, move_object, rotate_object, scale_object, rename_object), the absence of any routing signal leaves selection entirely to guesswork.

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