Skip to main content
Glama

device_knowledge

Look up Ableton Live devices and plug-ins for kind, purpose, key parameters, and uses, or browse native devices by kind with MIDI Tools API limitations noted.

Instructions

What a device does: a native Live device (from the Live 12 manual: kind, category, purpose, key parameters, electronic/techno uses, sidechain, tip), a bundled Max for Live device, or a known plug-in (e.g. "Acid V", "Comp FET-76", "Cthulhu"). Without name, the catalogue of native devices, optionally filtered by kind (instrument, audio_effect, midi_effect, max_for_live). Also says what Live 12's MIDI Tools are and that the API can't drive them.

Parameters:

  • name: Device or plug-in name

  • kind: Filter for the catalogue

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "device_knowledge"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
nameNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden; it does establish this is a read-only lookup and hints at coverage limits (MIDI Tools can't be driven via the API). However, it does not state what happens when `name` is unknown, how matching works (exact, case-sensitive, partial for plug-ins like "Acid V"), or whether the catalogue is static or introspected from the set.

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

Conciseness3/5

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

The first sentence is an overlong clause stack with a nested parenthetical field list, and the parameter notes at the bottom restate the schema titles with little added value. The useful content (two modes, kind enum, MIDI Tools limit) is present but not front-loaded cleanly.

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

Completeness3/5

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

An output schema exists, so return-value detail is not required — yet the description spends its opening on it while leaving the genuinely ambiguous points (name-matching rules, behavior on unknown names, relationship to sibling device tools) unaddressed. For a simple two-parameter read tool this is adequate but leaves real gaps.

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 0%, so the description must compensate, and it largely does: it supplies the four accepted `kind` values (instrument, audio_effect, midi_effect, max_for_live) that are absent from the schema, and it explains the mode switch governed by whether `name` is present. What it omits is name-matching semantics.

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

Purpose4/5

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

The description states a concrete purpose (returning knowledge about a named native Live device, Max for Live device, or plug-in) and a second mode (catalogue listing when `name` is omitted). It also enumerates the fields returned (kind, category, purpose, key parameters, uses, sidechain, tip), which makes the output shape predictable. It never mentions the near-identical siblings device_inventory or get_device_info, so an agent cannot distinguish it from them from the text alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied structurally: "Without `name`, the catalogue of native devices, optionally filtered by kind" conveys the two calling modes, and the MIDI Tools note signals a scope limit. There is no explicit when-to-use guidance, no statement of when to prefer this over device_inventory/get_device_info, and no prerequisites or failure behavior.

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