Skip to main content
Glama
Sign In
LiveSession MCP

LiveSession MCP

by Uri-Rosen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_browser_items_at_path

Read-only

Retrieve browser items at a specified Ableton path to inspect available categories, folders, and subfolders before selecting or loading content.

Instructions

Get browser items at a specific path in Ableton's browser.

Parameters:

  • path: Path in the format "category/folder/subfolder" where category is one of the available browser categories in Ableton

  • user_prompt: The original user prompt that led to this tool call (for telemetry)

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": {
      "path": "<path>"
    },
    "name": "get_browser_items_at_path"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
user_promptNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully carried by structured data. The description adds no behavioral context beyond that — nothing about invalid-path behavior, emptiness of results, or whether returned items are directly loadable. With annotations covering safety, a baseline 3 is appropriate.

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?

A single scope sentence followed by a short parameter block; the core purpose is front-loaded and nothing is padded. The bullet-list format is functional, though the user_prompt entry is low-value for tool selection.

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-shape explanation is not needed, and the read-only annotations cover the mutation risk. What remains missing is what a 'browser item' contains (URI/identifier usable with load_browser_uri), behavior on a nonexistent path, and how deep the path may recurse — details an agent needs to chain this call 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?

Schema description coverage is 0%, so the description must compensate, and it does: it specifies the path grammar "category/folder/subfolder" and constrains category to Ableton's available browser categories, which the bare `string` schema does not convey. The `user_prompt` telemetry parameter is also explained, though its optionality/default is left to the schema.

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 pairs a specific verb (Get) with a specific resource (browser items) and a scope (at a specific path in Ableton's browser). An agent can distinguish it from get_browser_tree or search_browser only by inference from the name, not from any explicit sibling differentiation in the text.

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?

There is no statement of when to use this tool versus the many browser siblings (get_browser_tree, search_browser, load_browser_uri, load_browser_uri, list_plugins). The path format hints at hierarchical drilling, but no prerequisites, exclusions, or alternatives are named.

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