Skip to main content
Glama

copy_object

Copy lighting console objects (cues, presets, groups) from source to target using grandMA2 selection expressions. Supports range copy and overwrite or merge modes.

Instructions

Copy an object (or range) to a new location.

``source`` and ``target`` accept grandMA2 selection expressions: a single ID
or a range/list using thru / + / - (e.g. "1 thru 10", "1 + 3 + 5"), so a
whole range copies in one call.

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

Returns:
    str: Operation result message

Examples:
    - Copy cue 1 to cue 10: object_type="cue", source="1", target="10"
    - Copy groups 1 thru 5 to 11: object_type="group", source="1 thru 5", target="11"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
object_typeYes
sourceYes
targetYes
modeNodefault

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations provided. Description discloses mode options (default/overwrite/merge) and that it returns a result message, but doesn't fully detail side effects of overwriting or potential destructive actions beyond mode parameter.

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

Conciseness5/5

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

Well-structured with clear purpose, Args section, Returns, and Examples. Each sentence adds value without redundancy.

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?

Covers all parameters, return type, and expression syntax. Could add more detail about behavior of 'overwrite' and 'merge' modes, but overall comprehensive for the tool's complexity.

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 coverage is 0%, so description fully compensates by explaining selection expressions, providing examples, and clarifying the meaning and usage of each parameter beyond the schema titles.

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?

Description clearly states 'Copy an object (or range) to a new location.' with specific verb and resource. Differentiates from sibling 'move_object' which moves rather than copies.

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

Usage Guidelines3/5

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

Implied usage via examples, but lacks explicit guidance on when to use this tool versus alternatives like 'move_object' or when not to use it.

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