Skip to main content
Glama

separate_objects

Split a mesh object into separate objects by loose parts to isolate disconnected geometry for editing, rigging, or export workflows.

Instructions

Separate a mesh object.

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

Input Schema

NameRequiredDescriptionDefault
modeNoLOOSE
nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the behavioral burden. It implies a mutation but does not say whether the original object is preserved, whether new objects are created, what mode means, or what preconditions such as object selection or edit mode are required.

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 single sentence is front-loaded and free of wasted wording, but it is under-specified for a mutation tool with two parameters. Brevity here comes at the cost of necessary structure and context.

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?

The output schema reduces the need to describe return values, but the definition remains incomplete for a mutation tool with no annotations and undocumented parameters. It lacks the mode semantics and behavioral effects an agent needs to invoke it safely and correctly.

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%, and the description does not explain either parameter. It weakly implies that `name` identifies the mesh object, but it gives no meaning for `mode` or its default value `LOOSE`, which is likely essential to correct invocation.

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 names a specific operation and target resource: separating a mesh object. It is meaningfully distinct from a sibling like join_objects, but it does not clarify what separation means in this context, such as splitting by loose parts or another mode.

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 guidance on when to use this tool, when not to use it, or which sibling tool might be more appropriate. An agent must infer its role from the name and the single sentence alone.

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