Skip to main content
Glama

join_objects

Combine multiple mesh objects into one, optionally specifying a target mesh, to simplify scene organization and editing.

Instructions

Join multiple mesh objects.

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

Input Schema

NameRequiredDescriptionDefault
namesYes
targetNo

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?

With no annotations provided, the description carries the full behavioral burden, yet it discloses nothing about the mutation's effects: whether source objects are removed from the scene, which object becomes the result, whether the operation is reversible, or how the required 'names' list interacts with the optional 'target'. All that is conveyed is the bare verb 'join'.

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 grammatically clean and front-loaded but is reduced to near-zero information rather than being appropriately concise. There is no waste because there is almost no content, which is under-specification rather than good compression.

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. Still, for a destructive scene-modifying operation with 0% parameter documentation and no annotations, the definition leaves out what an agent needs in order to call it correctly, notably the fate of the original objects and the role of 'target'.

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% and the description adds no meaning for either parameter. It never explains what 'names' contains (object names? required list of what size?) or what 'target' does (destination object? defaults to null — then what?). This is a significant gap for a two-parameter mutating tool.

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 names a concrete verb and resource ("Join multiple mesh objects"), so the agent can infer it merges meshes. However, it does not clarify what "join" means operationally (merge into a single object vs. group), nor does it differentiate it from siblings such as create_array_of_objects or separate_objects, which is the inverse operation.

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 statement of when to use this tool versus alternatives, no prerequisites (e.g., objects must be meshes, selection state), and no guidance on the inverse sibling separate_objects. The agent must infer usage entirely from the one-line purpose statement.

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