Skip to main content
Glama
FreeRiverHouse

AbletonMCP

by FreeRiverHouse
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

get_session_info

Retrieve current Ableton Live session details including tracks, instruments, and MIDI clips for music production management.

Instructions

Get detailed information about the current Ableton session

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • AbletonMCP_Remote_Script/__init__.py:344-360 (handler)
    The actual implementation of the tool logic that queries the Ableton Live object model for session info.
    def _get_session_info(self):
    """Get information about the current session"""
    try:
        result = {
            "tempo": self._song.tempo,
            "signature_numerator": self._song.signature_numerator,
            "signature_denominator": self._song.signature_denominator,
            "track_count": len(self._song.tracks),
            "return_track_count": len(self._song.return_tracks),
            "master_track": {
                "name": "Master",
                "volume": self._song.master_track.mixer_device.volume.value,
                "panning": self._song.master_track.mixer_device.panning.value
            }
        }
        return result
    except Exception as e:
  • MCP_Server/server.py:228-233 (handler)
    The MCP tool handler that invokes the remote script command via `_run`.
    def get_session_info(ctx: Context) -> str:
    """Get detailed information about the current Ableton session"""
    try:
        return json.dumps(_run("get_session_info"), indent=2)
    except Exception as e:
        return f"Error: {e}"

Tool Definition Quality

B3.2/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Get' implies a read operation, it doesn't specify whether this requires Ableton to be running, what format the information returns in, whether it's real-time or cached data, or any error conditions. This leaves significant gaps for a tool that presumably interacts with a live DAW session.

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?

The description is a single, efficient sentence that states exactly what the tool does with zero wasted words. It's appropriately sized for a zero-parameter tool and front-loads the essential information.

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?

For a zero-parameter tool with no output schema, the description provides the basic purpose but lacks important context. Given this likely interacts with a live Ableton session, it should mention requirements (e.g., Ableton running), return format expectations, or typical use cases. The absence of annotations means the description should compensate more than it does.

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

Parameters4/5

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

The tool has zero parameters, so there's no need to explain parameter semantics. With 100% schema coverage (though empty) and no parameters to document, the description appropriately focuses on the tool's purpose rather than parameter details.

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 tool's purpose with a specific verb ('Get') and resource ('detailed information about the current Ableton session'). It distinguishes from siblings like get_track_info or get_browser_items_at_path by focusing on session-level information rather than specific components. However, it doesn't explicitly contrast with these siblings in the description text itself.

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 prerequisites, timing considerations, or when other tools like get_track_info might be more appropriate. The agent must infer usage from the tool name and context alone.

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/FreeRiverHouse/ableton-flow'

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