Skip to main content
Glama
Sign In
ableton-mcp-lofifren

ableton-mcp-lofifren

by LofiFren
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_track_devices

Retrieve devices on a track with their parameters, including current value, min, and max, to discover parameter indices and ranges before adjusting them.

Instructions

List the devices loaded on a track, including each device's parameters with their current value, min, and max. Use this to discover parameter indices and ranges before calling set_device_parameter.

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": "get_track_devices"
  }
}

Input Schema

NameRequiredDescriptionDefault
track_indexYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Fully discloses that it returns each device's parameters with current value, min, and max. No annotations exist, so description carries full burden; it adequately describes behavior with no contradictions.

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 concise sentences with no redundant information. The first sentence states what the tool does, and the second provides usage guidance.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter tool with no output schema, the description completely covers the purpose, usage, and context. It references the sibling tool set_device_parameter, completing the usage workflow.

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?

Only one parameter (track_index) with no schema description. The parameter name is self-explanatory, but the description does not add extra meaning beyond the schema. With 0% schema coverage, the description should compensate, but it minimally does.

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 states the tool lists devices on a track with their parameters and values. The verb 'list' and resource 'track devices' are specific. Differentiates from siblings by mentioning use with set_device_parameter.

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?

Explicitly instructs to use this tool before calling set_device_parameter to discover parameter indices and ranges. Provides clear when-to-use and names an alternative tool.

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