Skip to main content
Glama

playlist_shuffle

Read or change playlist shuffle settings. Enabling it reorders playback without renumbering entries and keeps the current track playing.

Instructions

Get or set playlist shuffle. Enabling it reorders playback without renumbering entries, and keeps the current track playing. Call with no arguments to read the current setting.

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

Input Schema

NameRequiredDescriptionDefault
enabledNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the burden and does real work: it discloses that enabling reorders playback without renumbering entries and keeps the current track playing, which is exactly the side-effect an agent needs before toggling playback. It leaves out whether the change is persisted to disk or scoped to the current session.

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 tight sentences, front-loaded with the verb and resource, then the behavioral effect, then the no-argument read case. Nothing is redundant or wasted.

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 one-parameter toggle with no annotations and no output schema, the description covers purpose, both call modes, and the playback side effects. Only the persistence question and the read return value are left implicit, which is a modest gap at this complexity.

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?

The single boolean parameter has zero schema description coverage, so the description must compensate. It does explain the read/write split implied by optional 'enabled', but never states what enabled=true versus false does or what the read returns, so compensation is only partial.

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 pair and resource: get or set playlist shuffle. An agent can immediately tell this governs shuffle state as opposed to repeat or playback order in the sibling list. The only gap is that no sibling is named for contrast.

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 explains the two modes: call with no arguments to read, supply a value to set. That gives clear usage context for both paths. It doesn't state when not to use it (e.g., that shuffle state may need playlist_save to persist), so it stops short of full alternatives guidance.

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