Verify that the Ableton Live Remote Script version and capabilities match the MCP server package, ensuring a successful handshake and compatible bridge setup.
Report Ableton Remote Script version and capabilities (handshake).
Use this to verify the Live-side bridge matches this MCP server package.
| Name | Required | Description | Default |
|---|---|---|---|
| user_prompt | No |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v1.4.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It implies a read-only operation ('Report') and a handshake check, which suggests no side effects. However, it does not mention error conditions or what happens on mismatch. For a simple info retrieval tool, this is reasonably transparent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two concise sentences with zero waste. The main purpose is front-loaded, and the usage guidance follows immediately. It is well-structured and to the point.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool has an output schema, so return values need not be described. The description covers the core use case (verification) and the fact it is a handshake. However, it omits any explanation of the user_prompt parameter, which is a gap in completeness. Given the simplicity of the tool, this is a minor omission but still leaves the definition slightly incomplete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has one optional parameter (user_prompt) with a default, and schema description coverage is 0%. The description does not mention this parameter at all, leaving its purpose unclear. While the parameter is optional and defaults to empty, an agent might need to know whether to pass it or not. The description fails to compensate for the lack of schema documentation.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool reports Ableton Remote Script version and capabilities, with a specific verb (report) and resource. It also mentions 'handshake' which clarifies its role in verifying the bridge. This distinguishes it from the sibling tools which are about sessions, tracks, and playback.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives explicit guidance on when to use this tool: 'Use this to verify the Live-side bridge matches this MCP server package.' It provides a clear use case but does not mention alternatives or exclusions. Since the purpose is narrow and specific, this is adequate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.