Skip to main content
Glama
Sign In
LiveSession MCP

LiveSession MCP

by Uri-Rosen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_meters

Read-only

Read live peak levels (0.0–1.0) for all tracks, returns, and master during playback to detect clipping or quiet tracks without exporting.

Instructions

Live peak levels (0.0-1.0, 1.0 = 0 dBFS) of every track, return and the master, read right now. Call while playback runs to spot clipping or quiet tracks without exporting.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so the bar is lower. The description still adds real behavioral context: values are instantaneous ('read right now'), normalized to dBFS on a 0.0-1.0 scale, cover returns and master as well as tracks, and require active playback to be meaningful — none of which the annotations convey.

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 sentences, both earning their place: the first defines the measurement and its scale, the second gives the usage condition. Scope and semantics are front-loaded with no filler.

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?

This is a simple zero-argument read tool with an output schema that carries the return shape, and the description supplies everything else an agent needs: units, range, axis of measurement (tracks/returns/master), and the playback precondition.

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?

Zero parameters, so the baseline of 4 applies. The description does not need to explain arguments but productively spends its words on what the parameterless call returns instead.

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?

Names a specific verb ('read') and resource ('live peak levels of every track, return and the master'), and the parenthetical defines the scale (0.0-1.0, 1.0 = 0 dBFS). It implicitly separates itself from mixing/export tools but never names a sibling like get_mixer or get_session_snapshot, so the differentiation is inferential rather than explicit.

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?

'Call while playback runs' gives a concrete activation condition and 'without exporting' rules out the heavier alternative path. There is no explicit when-not guidance or named alternative tool, but the context is clear enough for correct selection.

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