Skip to main content
Glama
Sign In
LiveSession MCP

LiveSession MCP

by Uri-Rosen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

search_browser

Read-only

Search Ableton Live's entire browser for instruments, effects, sounds, drums, samples, plugins, packs, and user library items, then load a chosen result via load_browser_uri.

Instructions

Search Live's whole browser: instruments, audio_effects, midi_effects, sounds, drums, samples, plugins, user_library, packs. Load a result with load_browser_uri.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
categoriesNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, destructiveHint=false, and openWorldHint=false, so safety is covered; the description adds the scope statement ("whole browser") and the load hand-off. It does not describe result ordering, whether limited results are truncated, or how matching works (substring vs fuzzy), which would be the extra value beyond the annotations.

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 short sentences, front-loaded with the capability and closed with the next action. Every clause carries information; nothing is repeated from the schema or annotations.

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

Completeness4/5

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

A read-only search with a rich annotation set and an output schema, so return values need no explanation. The main residual gaps are the meaning of `limit` (default 40, no explanation) and whether `query` matches names, paths, or descriptions.

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?

Schema description coverage is 0%, so the description must carry the load. The enumerated list (instruments, audio_effects, ... packs) implicitly defines the valid values for the `categories` filter, which is genuinely helpful, but it never says so explicitly and says nothing at all about `limit` or the matching semantics of `query`.

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 gives a specific verb and resource ("Search Live's whole browser") and enumerates the content types covered, so an agent knows exactly what domain is being searched. It does not distinguish itself from near-neighbours like find_plugins, list_plugins, or get_browser_tree, which keeps it short of a 5.

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?

It supplies a concrete follow-up step ("Load a result with load_browser_uri"), which is a useful workflow cue for what to do after finding something. It never states when to prefer this over find_plugins, list_plugins, or get_browser_tree, so the alternative-selection guidance is only implied.

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