Skip to main content
Glama
Sign In
LiveSession MCP

LiveSession MCP

by Uri-Rosen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

load_browser_uri

Load a browser item (preset, sample, device, or kit) by URI onto a track, return, or master to place sounds and devices where needed.

Instructions

Load any browser item (preset, sample, device, kit) by URI onto a track, return or the master.

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": {
      "uri": "<uri>"
    },
    "name": "load_browser_uri"
  }
}

Input Schema

NameRequiredDescriptionDefault
uriYes
track_typeNotrack
track_indexNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful placement context (track, return, or master). However it says nothing about whether an existing device/clip at the target is replaced, what happens on an invalid URI, or whether loading is synchronous.

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 front-loaded sentence with no wasted wording, and the item types and destination targets come before any qualifiers. It is efficient, though it leaves no room for the usage and parameter detail the schema lacks.

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?

The existence of an output schema means return values need not be explained. But for a 3-parameter mutation tool with zero schema description coverage, the description omits the URI source, valid track_type values, and track_index meaning, leaving meaningful gaps for an agent to guess at.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for three parameters, so the description must compensate and only partially does: 'by URI' covers uri, and 'track, return or the master' hints at track_type values, but track_index is never mentioned and no accepted track_type values, index semantics, or URI format are given.

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?

States a specific verb (load) and resource (any browser item: preset, sample, device, kit) with an explicit identifier (URI) and target location (track, return, master). This differentiates it reasonably from siblings like load_sample or load_plugin, though it does not name those siblings directly.

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 when-to-use guidance and no routing to alternatives such as load_sample, load_plugin, load_drum_kit, or search_browser/get_browser_tree for obtaining a URI. The agent must infer that this tool is for URI-addressed loads and must already know where URIs come from.

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