Skip to main content
Glama

mymusik_playback

Control the current queue: resume or pause playback, skip to the next track, or go back one track. Requires playback access; use search tools to select specific songs, albums, or playlists.

Instructions

Control the current MyMusik queue. Resume or pause playback, skip to the next track, or go back one track. Requires playback access. To play a particular song, album or playlist by name, use the app's search and API tools.

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": {
      "action": "<action>"
    },
    "name": "mymusik_playback"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden. It does add the access prerequisite ('Requires playback access') and makes clear these are state-changing playback controls, but it says nothing about behavior when no device/queue is active, whether next/previous wrap at the queue boundaries, or what the call returns.

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?

Three short sentences, front-loaded with the resource and operations, then the access requirement, then the alternative routing. No filler or redundancy.

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 single-parameter tool with a self-documenting enum, no annotations, and no output schema, the description covers the operations, the access prerequisite, and the alternative route. The main gap is what happens on boundary or inactive-playback conditions.

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

Parameters3/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 partially does by restating the four enum values in prose with meaning ('skip to the next track', 'go back one track'). However, it adds little beyond the enum itself, such as any action-specific preconditions or effects.

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?

The description states a specific verb (control) and resource (MyMusik queue/pb) and enumerates the exact operations: resume, pause, next, previous. It also distinguishes the tool from the app's search/API tools used to play a named song, album, or playlist, so an agent can tell what this tool is and is not for.

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?

It gives clear usage context ('Control the current MyMusik queue') and an explicit redirect for the out-of-scope case ('To play a particular song, album or playlist by name, use the app's search and API tools'). The alternative is described generically rather than by a named tool, and there is no guidance for edge cases like nothing currently playing.

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