Skip to main content
Glama

organize_scene

Group scene objects into logical collections to keep Blender projects structured and easier to manage.

Instructions

Organize objects into logical collections.

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": "organize_scene"
  }
}

Input Schema

NameRequiredDescriptionDefault
structureNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.2/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 burden of behavioral disclosure. It implies an organizational mutation but does not state whether existing collections are replaced or extended, whether all or selected objects are affected, what happens to objects not included, or what side effects the operation has.

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?

The definition is a single front-loaded sentence with no wasted words, which is structurally clean. However, it is under-specified for a tool whose behavior and parameter semantics need explanation, so its brevity reflects omission rather than optimal concision.

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 the input schema contains a complex optional 'structure' parameter with no description coverage. Combined with the absence of annotations and the lack of behavioral detail, the description is not complete enough to guide reliable invocation.

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?

The sole parameter, 'structure,' has 0% schema description coverage and is not mentioned in the description at all. Its nested object-of-string-arrays shape and its null default must be inferred entirely from the raw schema, so the description adds no meaning beyond the schema.

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 states the broad action, 'Organize objects into logical collections,' but 'logical collections' is undefined and it does not clarify what kind of scene organization is performed. It gives a vague sense of purpose rather than a precise verb-plus-resource distinction from siblings such as get_scene_hierarchy or export_scene.

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 explicit when-to-use guidance, no when-not guidance, and no named alternatives among the many sibling scene tools. At best, an agent can infer that this tool is for organizing objects, but the description does not explain when that operation is appropriate versus using hierarchy or export tools.

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