Skip to main content
Glama

playlist_repeat

Read or set the playlist repeat mode: off stops after the last entry, one loops the current file, and all wraps around.

Instructions

Get or set the playlist repeat mode. 'off' stops after the last entry, 'one' loops the current file, 'all' wraps around. Call with no arguments to read the current mode.

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

Input Schema

NameRequiredDescriptionDefault
modeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the full behavioral burden; it does disclose the dual read/write nature and exactly what each setting does to playback. It omits whether the setting persists across sessions, whether a playlist must be loaded first, and what the read call returns beyond 'the current mode'.

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?

Three short sentences, front-loaded with purpose followed by value semantics and then the read-mode instruction. Every sentence adds information; only minor structure gain would come from grouping the enum definitions more tightly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter tool with no output schema and no annotations, the essentials (purpose, enum meanings, no-arg read behavior) are covered. Persistence and preconditions for a player-state mutation are left unstated, which matters given no annotations to fall back on.

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

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, yet the description defines every enum value in plain language ('off' stops after the last entry, 'one' loops the current file, 'all' wraps around), fully compensating for the bare schema. The lone optional parameter is thereby unambiguous.

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 verb pair (get/set) and a precise resource (playlist repeat mode), and the enum vocabulary ('off', 'one', 'all') makes it immediately distinguishable from siblings like ab_loop or playlist_shuffle.

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 tells the agent how to invoke the read path ('Call with no arguments to read the current mode') and implies the write path via the mode argument, so the two usage modes are clear. It stops short of naming when to prefer a sibling or any precondition such as an active playlist.

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