Skip to main content
Glama

get_track_info

Retrieve detailed information about a specific track in Ableton Live sessions to analyze track properties and settings.

Instructions

Get detailed information about a specific track in Ableton.

Parameters:

  • track_index: The index of the track to get information about

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
track_indexYes

Implementation Reference

  • MCP tool handler for 'get_track_info'. Connects to Ableton remote script via socket, sends command with track_index, receives and returns JSON-formatted track details.
    @mcp.tool()
    def get_track_info(ctx: Context, track_index: int) -> str:
        """
        Get detailed information about a specific track in Ableton.
        
        Parameters:
        - track_index: The index of the track to get information about
        """
        try:
            ableton = get_ableton_connection()
            result = ableton.send_command("get_track_info", {"track_index": track_index})
            return json.dumps(result, indent=2)
        except Exception as e:
            logger.error(f"Error getting track info from Ableton: {str(e)}")
            return f"Error getting track info: {str(e)}"
  • Core Ableton Live API implementation for retrieving detailed track information, including clip slots and devices. Called by the remote script when receiving 'get_track_info' command.
    def _get_track_info(self, track_index):
        """Get information about a track"""
        try:
            if track_index < 0 or track_index >= len(self._song.tracks):
                raise IndexError("Track index out of range")
            
            track = self._song.tracks[track_index]
            
            # Get clip slots
            clip_slots = []
            for slot_index, slot in enumerate(track.clip_slots):
                clip_info = None
                if slot.has_clip:
                    clip = slot.clip
                    clip_info = {
                        "name": clip.name,
                        "length": clip.length,
                        "is_playing": clip.is_playing,
                        "is_recording": clip.is_recording
                    }
                
                clip_slots.append({
                    "index": slot_index,
                    "has_clip": slot.has_clip,
                    "clip": clip_info
                })
            
            # Get devices
            devices = []
            for device_index, device in enumerate(track.devices):
                devices.append({
                    "index": device_index,
                    "name": device.name,
                    "class_name": device.class_name,
                    "type": self._get_device_type(device)
                })
            
            result = {
                "index": track_index,
                "name": track.name,
                "is_audio_track": track.has_audio_input,
                "is_midi_track": track.has_midi_input,
                "mute": track.mute,
                "solo": track.solo,
                "arm": track.arm,
                "volume": track.mixer_device.volume.value,
                "panning": track.mixer_device.panning.value,
                "clip_slots": clip_slots,
                "devices": devices
            }
            return result
        except Exception as e:
            self.log_message("Error getting track info: " + str(e))
            raise
  • Dispatch/registration in remote script's command processor: handles 'get_track_info' command by extracting track_index and calling _get_track_info.
    elif command_type == "get_track_info":
        track_index = params.get("track_index", 0)
        response["result"] = self._get_track_info(track_index)
  • Input schema documentation in the MCP tool docstring, specifying the track_index parameter.
    """
    Get detailed information about a specific track in Ableton.
    
    Parameters:
    - track_index: The index of the track to get information about
    """
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states this is a 'get' operation but doesn't disclose behavioral traits like whether it's read-only, safe to call frequently, requires specific Ableton state, or what happens with invalid track indices. For a tool with zero annotation coverage, this is a significant gap.

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 appropriately sized with two sentences: one stating the purpose and one listing parameters. It's front-loaded with the core function. The parameter listing is clear but could be integrated more seamlessly.

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 no annotations, no output schema, and low schema coverage, the description is incomplete. It doesn't explain what 'detailed information' includes (e.g., track name, devices, clips), error handling, or dependencies. For a tool in a music production context with siblings that modify state, more behavioral context is needed.

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 description must compensate. It adds meaning by explaining 'track_index' as 'The index of the track to get information about', which clarifies the parameter's purpose beyond the schema's title 'Track Index'. However, it doesn't provide format details like valid ranges or indexing conventions.

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 clearly states the verb 'Get' and resource 'detailed information about a specific track in Ableton', making the purpose understandable. However, it doesn't differentiate from sibling tools like 'get_session_info' or 'get_browser_items_at_path', which also retrieve information but about different resources.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'get_session_info' (which might provide broader session data) or clarify if this is for detailed track metadata versus basic info available elsewhere.

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

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