Skip to main content
Glama

get_tracks_overview

Retrieve a compact overview of all tracks, return tracks, and the master—names, colors, groups, routing, volume, pan, mute, and solo—before organizing a session.

Instructions

Compact overview of every track, return track and the master: index, name, color (#RRGGBB), whether it is a group, which group it belongs to, output routing, volume (dB text), pan, mute and solo. Use this before organizing a session; it is much cheaper than calling get_track_info per track.

Parameters:

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

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

Input Schema

NameRequiredDescriptionDefault
user_promptNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.5.1

TDQS

A4.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it discloses the read-only character implicitly and adds a useful cost/performance trait ('much cheaper'). It says nothing about permissions, session requirements, or freshness of the snapshot, and the field list partly restates what the output schema already provides.

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?

Front-loads the payload contents, then the when-to-use rationale, then parameter notes — a sensible order with little waste. The long field enumeration is the only slightly heavy part, though it aids scanning.

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?

An output schema exists, so return values need no explanation, yet the description still summarizes them for quick orientation, and usage plus the sole parameter are covered. It is complete enough for an agent to call correctly; only permission/session prerequisites are unaddressed.

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 coverage is 0% for the single parameter, so the description must compensate, and it does by explaining that user_prompt is the originating prompt used for telemetry — a non-obvious meaning an agent cannot guess from the name 'user_prompt'. It omits that the parameter is optional with an empty-string default.

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 concrete verb and resource ('overview of every track, return track and the master') and enumerates the fields returned, so the agent knows exactly what snapshot it gets. It explicitly contrasts itself with the sibling get_track_info, making the two distinguishable without opening either schema.

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?

Gives a clear when-to-use rule ('Use this before organizing a session') and names the alternative plus the cost reason ('much cheaper than calling get_track_info per track'). No explicit when-not condition or prerequisite, so it falls just short of the top band.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.