Skip to main content
Glama
bschoepke

ableton-live-mcp

by bschoepke

live_children

Retrieve child objects from a specified Ableton Live object using its path and ID.

Instructions

List child objects from a collection.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
refYes
childYes
limitNo
detailNo
max_itemsNo
max_depthNo
max_string_lengthNo
timeoutNoSeconds to wait for Live's main thread.

Implementation Reference

  • Handler function _rpc_children: resolves the object ref, gets the named child collection, takes up to 'limit' items, returns object summaries (with truncation marker if needed). This is the actual execution logic invoked when the live_children tool is called.
    def _rpc_children(self, params):
        obj = self._resolve(params.get("ref"))
        limit = params.get("limit")
        values, truncated = self._take(getattr(obj, params["child"]), limit)
        result = [self._object_summary(child, self._detail(params)) for child in values]
        if truncated:
            result.append({"truncated": True})
        return result
  • src/server.py:92-97 (registration)
    Registration of the 'live_children' MCP tool on the server. Defines the input schema (ref, child, limit, plus response controls) and binds it to the 'children' bridge method via the forward() helper.
    server.add_tool(Tool("live_children", "List child objects from a collection.", schema({
        "ref": ref,
        "child": {"type": "string"},
        "limit": {"type": "integer", "minimum": 0},
        **response_controls,
    }, ["ref", "child"]), forward("children")))
  • Input schema for live_children: requires 'ref' (object reference with path/id) and 'child' (string name of child collection), optional 'limit' (integer >=0) and response controls (detail, max_items, max_depth, max_string_length, timeout).
        "ref": ref,
        "child": {"type": "string"},
        "limit": {"type": "integer", "minimum": 0},
        **response_controls,
    }, ["ref", "child"]), forward("children")))
  • Helper _take used by _rpc_children: limits collection to DEFAULT_CHILD_LIMIT (200) if no limit given, returns (items, truncated) tuple.
    def _take(self, values, limit):
        if limit is None:
            limit = DEFAULT_CHILD_LIMIT
        if limit is not None and limit < 0:
            return list(values), False
        result = []
        for index, value in enumerate(values):
            if index >= limit:
                return result, True
            result.append(value)
        return result, False
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only says 'List child objects,' missing details about side effects, permissions, or that it is a read-only operation. The timeout parameter hint is in schema, not description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely short (one sentence) but underspecified. While concise, it fails to provide necessary detail, making it unhelpful.

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

Completeness1/5

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

Given 8 parameters, nested objects, no output schema, and no annotations, the description is completely inadequate. It doesn't explain the tool's role in Live's API or how to use the parameters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 13%, with only timeout described. The description adds no information about any parameters, leaving the agent to guess meanings of ref, child, limit, etc.

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

Purpose3/5

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

The description specifies a verb (List) and resource (child objects from a collection), but 'collection' is vague and doesn't clarify the context (Ableton Live hierarchy). It provides minimal distinction from sibling tools like live_get or live_browser_roots.

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 or when not to use it. The description lacks any context for usage scenarios.

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/bschoepke/ableton-live-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server