Skip to main content
Glama

move_object_to_collection

Move a Blender object into a specified collection, optionally making it exclusive to that collection.

Instructions

Move an object into a collection.

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>",
      "collection": "<collection>"
    },
    "name": "move_object_to_collection"
  }
}

Input Schema

NameRequiredDescriptionDefault
exclusiveNo
collectionYes
object_nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the whole behavioral burden, yet it says nothing about whether the object is removed from its prior collection, what happens if the target collection is missing, or whether the operation is reversible. The default-true 'exclusive' flag is a significant behavioral lever that goes entirely undisclosed.

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?

One short, front-loaded sentence with no wasted words, but the brevity is under-specification rather than efficiency. There is room for a clarifying clause without bloat.

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 described, but a mutation tool with zero annotations and zero parameter documentation should explain membership semantics and failure modes. As written, an agent cannot call this confidently without inspecting the schema and guessing at 'exclusive'.

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% across three parameters, and the description mentions none of them. In particular 'exclusive' (boolean, default true) is semantically opaque and is the one parameter an agent most needs explained; nothing here compensates for the schema gap.

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 concrete verb and resource ("Move an object into a collection") that an agent can act on. It does not distinguish this from the sibling move_object or explain how the two differ, so it stops short of full sibling differentiation.

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 on when to use this instead of move_object, create_collection, or set_object_parent, and no prerequisites (does the collection need to exist first?). The single clause leaves the agent to infer all routing decisions.

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