dzstudio-mcp

Overview Schema Source Related Servers Discussions Admin

create_objects

Create groups and 3D objects in one call, placing objects by position, orientation, and scale under new group refs or existing groups; objects stay held until released or reviewed.

Instructions

Create groups and objects as one step. New groups get a ref you can use as the group of objects in the same call; an object group may also be an existing group id or name. Position [x, y, z] in m, orientation [yaw, pitch, roll] in degrees, scale (default 1). The new objects are held by you until you release them or ask for review.

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

Input Schema

Name	Required	Description
`groups`	No
`objects`	No
`session`	No	Session handle (s1, s2 …) or session id; default: the current session

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.3Nov 8, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations, the description carries the full burden, and it does substantial work: it discloses the lifecycle constraint that created objects are held by the caller until release or review, plus coordinate units (meters, degrees) and the default scale. It omits permissions/visibility of new objects and whether creation is reversible or atomic on partial failure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four compact sentences, purpose front-loaded, no filler. The coordinate/units sentence is telegraphic to the point of requiring careful parsing, which slightly hurts scannability but not accuracy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no annotations and no output schema, the definition covers lifecycle and geometry semantics but says nothing about what is returned (created ids/refs) or error behavior. Adequate to call correctly on the happy path, incomplete for an agent needing to verify results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 33%, so the description must compensate, and it does partially: it supplies units for position, the yaw/pitch/roll ordering for orientation, the scale default of 1, and the ref-resolution rule for 'group'. However, 'class' and 'ref' semantics are left unexplained, and the session parameter is only covered by the schema itself.

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 opens with a specific verb and resource: 'Create groups and objects as one step,' which makes the combined/atomic nature of the operation clear at a glance. It does not explicitly distinguish itself from siblings like modify_objects or delete_objects, but the creation-plus-grouping scope is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the key usage context: new groups get a ref usable in the same call, and existing groups can be referenced by id or name. The closing sentence names the follow-up paths (release them or ask for review), implicitly routing the agent to those siblings. No explicit when-not-to-use guidance is given, which keeps it below a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.