Skip to main content
Glama

get_track_meters

Reads current output meter levels for every track, return track, and the main track on a 0.0-1.0 scale while the song plays, letting you monitor mix levels live.

Instructions

Live's output meters right now for every track, return track and the main track (0.0-1.0 on Live's meter scale, as in the mixer). Meaningful while the song plays; listen_to_arrangement samples them for you.

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_track_meters"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries full disclosure burden and does well: it establishes this is an instantaneous live reading (not historical or averaged), covers all track classes including return and main, and defines the value range and scale. It doesn't state what is returned when transport is stopped (presumably zeros), which is the main remaining ambiguity.

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 compact sentences with zero filler; the scope and units come first, the temporal caveat and alternative follow. Every clause carries information an agent would otherwise have to guess.

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?

For a simple zero-argument read with an output schema, this is nearly complete: scope, units, and timing semantics are all present. The one omission is behavior when playback is stopped, which matters for interpreting all-zero readings.

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?

The tool takes zero parameters, so there is nothing to disambiguate beyond the tool's scope, which the description already covers explicitly (all tracks, returns, main). Baseline 4 applies for a parameterless tool.

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?

States a specific resource and full scope: output meters for every track, return track, and the main track, and pins the scale (0.0-1.0, as in the mixer). It also names the sibling (listen_to_arrangement) that serves the related but different sampling use case, so an agent can separate the two without opening schemas.

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?

Explicitly frames usage context: meaningful while the song plays, and directs the agent to listen_to_arrangement when it wants sampled readings over time. The only gap is that it doesn't outright warn against polling this tool in a loop, though the alternative mention strongly implies it.

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