Skip to main content
Glama
Sign In
AbletonMCP

AbletonMCP

by juampicosta
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_devices

Retrieve a list of all plugins on a specific track, including their name, type, and number of parameters.

Instructions

List all devices (plugins) on a track with their name, type, and parameter count.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "track_index": "<track_index>"
    },
    "name": "list_devices"
  }
}

Input Schema

NameRequiredDescriptionDefault
track_indexYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. Only states it lists devices with attributes; no disclosure of error behavior, side effects, or requirements (e.g., track must exist).

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?

Single 14-word sentence, front-loaded with action verb 'List'. No redundant information.

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?

For a simple list tool with output schema, description is mostly adequate. Lacks error condition details (e.g., invalid track_index), but overall covers essential purpose and parameters.

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 has 0% description coverage. Description adds context that track_index refers to a track, but does not clarify index base (0-based?) or other constraints. Adds partial meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly specifies verb 'List', resource 'all devices (plugins) on a track', and output fields (name, type, parameter count). Distinguishes from siblings like 'get_device' and 'list_drum_pads'.

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?

No guidance on when to use this tool versus alternatives like 'get_device' or 'list_parameters'. Does not specify prerequisites or conditions for use.

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