Skip to main content
Glama

find_in_library

Read-onlyIdempotent

Search Ableton Live's browser for devices, presets, and samples by name and return file paths for loading. Locates Core Library, Pack, and User Library items for device setup.

Instructions

Search Live's browser: devices, presets (.adg, .adv) and samples in the Core Library, Packs and User Library. Returns paths for load_device.

The first search walks the whole browser (about 5 s, Live pauses briefly); later ones are instant. Exact names come first. Places are not searchable: Live does not show them to scripts.

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": {
      "query": "<query>"
    },
    "name": "find_in_library"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoOnly one part of the browser; any searches all.any
limitNoAt most this many results. Empty or 0: all results.
queryYesWords in the name, e.g. electric bass, reverb
refreshNoWalk the browser again after adding presets or packs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description adds genuinely useful behavior beyond them: first-search cost (~5 s, Live pauses briefly), subsequent searches being instant, and exact-name matches ranking first. That is real added context, but return shape and result-ordering details beyond 'exact names first' are thin, so it sits at a solid 3 rather than a 4.

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?

Front-loaded with what it searches, then the payoff (paths for load_device), then operational caveats. Four short sentences, nothing repeated, and the cost warning is placed where an agent will read it before calling.

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?

There is no output schema, but the description still says what comes back (paths consumable by load_device), how long the first call takes and why, and what is out of scope. Combined with a fully documented 4-parameter schema, an agent has everything needed to call this correctly.

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?

With 100% schema coverage the baseline is 3, and the description earns a bit more by explaining the caching model that motivates `refresh` ('The first search walks the whole browser... later ones are instant') and by naming the concrete preset file types the search covers. It still says nothing about `kind` or `limit` semantics, leaving those entirely to the schema.

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?

Specific verb plus resource plus scope: 'Search Live's browser: devices, presets (.adg, .adv) and samples in the Core Library, Packs and User Library.' It also states the outcome ('Returns paths for load_device'), which distinguishes it from the read_*/inspect_preset_file siblings that inspect content rather than locate it.

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

Usage Guidelines4/5

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

It implies the workflow (find first, then hand the path to load_device) and gives an explicit exclusion: 'Places are not searchable: Live does not show them to scripts,' which prevents a futile attempt. It does not, however, say when to prefer inspect_preset_file or read_device over a browse-search.

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