Skip to main content
Glama

get_session_info

Retrieve current Ableton Live session details including tracks, devices, and settings to analyze and manage your music production project.

Instructions

Get detailed information about the current Ableton session

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler function that executes the 'get_session_info' tool by sending the command to the Ableton remote script via socket and returning the JSON-formatted result.
    def get_session_info(ctx: Context) -> str:
        """Get detailed information about the current Ableton session"""
        try:
            ableton = get_ableton_connection()
            result = ableton.send_command("get_session_info")
            return json.dumps(result, indent=2)
        except Exception as e:
            logger.error(f"Error getting session info from Ableton: {str(e)}")
            return f"Error getting session info: {str(e)}"
  • Helper function in the Ableton remote script that retrieves and returns detailed session information using the Ableton Live API.
    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:
            self.log_message("Error getting session info: " + str(e))
            raise
  • Creation of the FastMCP server instance where tools like 'get_session_info' are registered via @mcp.tool() decorators.
    mcp = FastMCP(
        "AbletonMCP",
        description="Ableton Live integration through the Model Context Protocol",
        lifespan=server_lifespan
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves 'detailed information' but doesn't specify what that includes (e.g., tempo, tracks, clips, file path), whether it's read-only (implied by 'Get'), or any performance considerations. This leaves significant gaps for an agent to understand the tool's behavior.

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, clear sentence that directly states the tool's purpose without any fluff or unnecessary details. It's front-loaded and appropriately sized for a zero-parameter tool, making it easy for an agent to parse quickly.

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 lack of annotations and output schema, the description is incomplete for a tool that presumably returns complex session data. It doesn't hint at the structure or content of the returned information (e.g., JSON object with fields like tempo, tracks), which could help an agent interpret results. For a read operation with no structured output, more context is needed.

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 0 parameters, and the schema description coverage is 100%, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, which is efficient and avoids redundancy. A baseline of 4 is applied since there are no parameters to document.

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 the current Ableton session'), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'get_track_info' or 'get_browser_tree', which also retrieve session-related information but with different scopes.

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. For example, it doesn't specify if this should be used for general session metadata versus more specific tools like 'get_track_info' for track-level details or 'get_browser_tree' for file structure. There's no mention of prerequisites or contextual triggers.

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