Skip to main content
Glama

get_remote_script_info

Compares the Ableton control surface's version and commands with this server to diagnose outdated or unresponsive Live connections; use it when tools report compatibility or response issues.

Instructions

Version and command list of the AbletonStudioMCP control surface running in Live, compared with this server. Use it when tools say Live is too old or not responding (ableton-studio-mcp doctor checks the whole setup).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_remote_script_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden, and it does disclose that the payload is a diagnostic comparison between the remote script in Live and this server, implying a read-only, side-effect-free probe. It stops short of stating what a mismatch means or what the caller should do about it.

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?

Two short sentences: what it returns first, then the condition that should drive selection. Every clause carries information and the diagnostic pointer is a useful addition rather than filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 need not be explained, and the description supplies both the diagnostic purpose and the failure condition that motivates a call. The only gap is guidance on interpreting a version mismatch or what to do after seeing one.

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 takes zero parameters, so the baseline applies; there is nothing for the description to disambiguate and it correctly spends no words on arguments.

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?

Names a specific resource: the version and command list of the AbletonStudioMCP control surface running inside Live, plus how it compares to this server. That is far more concrete than the surrounding get_*_info siblings and lets an agent tell it apart, though the opening is a noun fragment rather than a verb-led statement.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger: use it when other tools report that Live is too old or not responding. It also points to the appropriate broader alternative, `ableton-studio-mcp doctor`, for checking the whole setup, so the escalation path is unambiguous.

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