Skip to main content
Glama

lom_describe

Read-onlyIdempotent

Reflect on any Ableton Live object to discover its class, properties, child collections, and callable methods. Use this to inspect unknown objects and identify available properties to read or modify.

Instructions

Reflect on any LOM object: class, properties, children, callable methods.

The raw reflection, reporting what the object itself declares. Use it to find
the property names on an object the catalog does not cover, then read them with
lom_get and write them with lom_set.

Returns:
    Dictionary reporting object class, properties, child collections with their
    counts, and the methods the Remote Script allowlist will let you call.

Note:
    For a device, prefer ``describe`` with ``with_parameters=True``. This tool
    reports a device's ``parameters`` child as a count, and a count is exactly
    what a Live ``Vector`` that refuses ``len()`` fails to give, so a plug-in
    with parameters can be reported as having none. ``describe`` falls back to
    probing indices when that happens and says which answer it is handing back.

    The methods listed here are names, not calls: invoke one through lom_call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesDotted LOM path to the object to reflect on: 'song', 'song.tracks[0]', 'song.tracks[0].devices[1]'.
depthNoHow many levels of child collection to walk. 1 reports the children of the addressed object only. Raising it multiplies the work and the cost is unmeasured.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changedv0.1.1
    • addedInput schema / properties / depth / description
      Added value: +"How many levels of child collection to walk. 1 reports the children of the addressed object only. Raising it multiplies the work and the cost is unmeasured."
    • addedInput schema / properties / path / description
      Added value: +"Dotted LOM path to the object to reflect on: 'song', 'song.tracks[0]', 'song.tracks[0].devices[1]'."
  2. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already mark this as read-only and idempotent. The description adds important behavior beyond that: it reports child collections as counts, warns that device parameters may be misreported as zero due to Live Vector len() issues, clarifies that describe falls back to index probing, and states that listed methods are names, not calls. This is meaningful, non-obvious behavioral context.

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

Conciseness4/5

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

The description is organized with clear sections, front-loads the core purpose, and uses the note only for a genuinely important caveat. There is some redundancy between the opening sentence and the 'Returns' paragraph, both covering class, properties, children, and methods, but overall the structure is deliberate and every major block earns its place.

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?

Given the output schema exists, the description does not need to explain return values in full, but it still covers the key behavioral details: what the dictionary contains, how methods are represented, when to prefer another tool, and an important failure mode. For this tool's complexity, nothing critical is missing.

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?

Schema coverage is 100%, so the baseline is 3. The description adds value beyond the schema by warning that raising depth multiplies the work and that the cost is unmeasured, which is not present in the parameter schema. It also reinforces the path semantics with examples already in the schema, but the depth warning is a genuine extra.

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?

The description opens with a specific verb and resource: 'Reflect on any LOM object: class, properties, children, callable methods.' It clearly distinguishes itself from related tools by explaining that this is raw reflection rather than reading or writing property values, and explicitly names lom_get, lom_set, and lom_call for those actions.

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?

The description gives explicit guidance on when to use this tool: to find property names the catalog does not cover, with follow-up reads via lom_get and writes via lom_set. It also gives a strong exclusion: for devices, prefer 'describe' with with_parameters=True, and explains why. This is clear routing among siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

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/romanstark/live-maestro'

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