Skip to main content
Glama

move_object

Relocate any lighting object (cue, preset, group, etc.) to a new position by cutting from its source. Supports range selection expressions for moving multiple items at once.

Instructions

Move an object (or range) to a new location. WARNING: removes from source.

``source`` and ``target`` accept selection expressions (thru / + / -), so a
whole range moves in one call (e.g. move groups 1 thru 10 to 21).

Args:
    object_type: Object type ("cue", "preset", "group", "sequence", "macro", ...)
    source: Source selection expression
    target: Target selection expression

Returns:
    str: Operation result message

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
object_typeYes
sourceYes
targetYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description carries full burden. It discloses that the tool is destructive ('removes from source'), supports range moves via selection expressions, and returns a result message. It adds value beyond the schema by explaining these behaviors. Could mention reversibility or failure modes, but adequate.

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?

The description is well-structured with a warning, explanation, and Args/Returns section. It is front-loaded with critical info. Slightly verbose but each sentence serves a purpose. Could be tightened but effective.

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

Completeness4/5

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

Given 3 required parameters, no annotations, and existence of output schema (though not detailed), the description covers core behavior, parameter meanings, selection expressions, and return type. It lacks examples or edge-case handling, but for an AI agent it provides sufficient context to use the tool correctly.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must compensate. It provides clear meanings for all three parameters: object_type with examples, source and target as selection expressions. Additionally, it explains selection expressions in the main text, adding significant value beyond the bare schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool moves an object (or range) to a new location, using the verb 'Move' and specifying the resource 'object (or range)'. The warning 'removes from source' distinguishes it from a copy operation, and the sibling list includes 'copy_object', enhancing differentiation.

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?

The description explains that the tool is for moving, not copying, via the warning 'removes from source'. It also describes selection expressions for ranges. However, it does not explicitly say when not to use it or mention alternatives like 'copy_object' by name, leaving some ambiguity.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/chienchuanw/gma2-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server