Skip to main content
Glama

duplicate_session_to_arrangement

Copy a session view clip to a specified beat position on the arrangement timeline.

Instructions

Copy a session view clip to the arrangement timeline. destination_time is the position in beats where the clip will be placed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
track_indexYes
clip_indexYes
destination_timeYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

Without annotations, the description carries full burden but only discloses the destination_time parameter. It fails to mention whether the original clip is modified, how overlapping clips are handled, undo behavior, or any side effects.

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 short and to the point, with two sentences. However, it could be more structured by listing all parameters or providing a brief example.

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?

Given the tool's complexity and zero annotations, the description lacks essential details: what happens to the source clip, whether the destination clip is created or overwritten, and how the operation affects the project. An output schema exists but is not leveraged here.

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 coverage is 0%, so description must compensate. It explains 'destination_time' but omits descriptions for 'track_index' and 'clip_index', which are not self-explanatory (e.g., zero-based vs one-based).

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 copies a session view clip to the arrangement timeline, specifying the verb and resource. It distinguishes itself from siblings like 'duplicate_arrangement_clip' and 'session_to_arrangement' by targeting a specific clip rather than the entire session.

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?

No guidance is provided on when to use this tool versus alternatives like 'session_to_arrangement' or 'duplicate_arrangement_clip'. There is no mention of prerequisites, exclusions, or preferred contexts.

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/amamparo/ableton-mcp'

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