Skip to main content
Glama

get_audio_clip_file

Retrieves the audio file path, length, and sample rate for an arrangement or Session clip on a track, so you can locate and process the underlying audio.

Instructions

Path of the audio file behind an audio clip (for example a take just recorded with record_arrangement), with its length and sample rate.

Parameters:

  • track_index: The track holding the clip

  • clip_index: Arrangement clip index (get_arrangement_clips) or Session slot

  • location: "arrangement" (default) or "session"

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": {
      "track_index": "<track_index>",
      "clip_index": "<clip_index>"
    },
    "name": "get_audio_clip_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
locationNoarrangement
clip_indexYes
track_indexYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

B3.2/5.0
Behavior2/5

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

No annotations exist, so the description carries the full disclosure burden. It states the returned fields but says nothing about failure modes (missing clip, MIDI clip, invalid session slot), whether the path is absolute or relative, or whether it errors when location is 'session' but no slot exists. Only the default for location is disclosed.

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?

Front-loaded one-line purpose followed by a compact parameter list; every line carries information. Slight redundancy in repeating the default for location that already appears in the schema.

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?

An output schema exists, so return values needn't be spelled out, and all three parameters are covered. What's missing is behavioral context an agent would need before calling — error conditions, and how clip_index differs between arrangement and session modes.

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 description coverage is 0%, so the parameter block is the only source of meaning and it does define all three: track_index (holding track), clip_index (arrangement index or session slot), and location with its default and two allowed values. That is solid, but it leaves clip_index ambiguous between the two location modes — no guidance on how a session slot is identified.

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 names the specific resource it retrieves – the file path behind an audio clip – plus the extra return fields (length, sample rate). That is concrete enough to distinguish it from reader siblings like get_clip_warp or get_clip_loop. It stops short of a clean verb-first statement, opening with a noun phrase ("Path of the audio file").

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?

Usage is implied through the cross-references: it points to record_arrangement as the way a take arrives and to get_arrangement_clips as the source of valid clip indices. However, it never says when to prefer this over analyze_audio_file or analyze_clip_music, and it gives no exclusion for non-audio clips.

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