vlc-mcp

by jaseonline

Overview Schema Source Related Servers Discussions Admin

Python

Local

toggle_playlist_mode

Toggle shuffle, loop, or repeat modes for VLC playlists and report the new state.

Instructions

Toggle a playlist mode on or off and report its new state.

Args: mode: "random" (shuffle), "loop" (repeat whole playlist) or "repeat" (repeat current item)

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": {
      "mode": "<mode>"
    },
    "name": "toggle_playlist_mode"
  }
}

Input Schema

Name	Required	Description	Default
`mode`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 12, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, the description carries full behavioral burden. It does disclose the mutation nature (state flip) and that a new state is reported, but is silent on whether the modes are mutually exclusive, whether toggling one affects another, and whether the state persists across sessions — significant unknowns for a state-changing tool.

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?

Two short elements: a front-loaded purpose sentence and an Args block. Nothing wasted, but the docstring-style formatting is slightly heavier than needed for a single-parameter tool.

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?

An output schema exists, so return values need not be explained, and the tool's complexity is low. The remaining gap is the mutual exclusivity/interaction semantics between the three modes, which an agent needs to pick the right value.

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% and there is no enum, so the description supplies essential meaning: 'random' means shuffle, 'loop' repeats the whole playlist, 'repeat' repeats the current item. It disambiguates loop vs repeat, which the schema cannot. It does not cover invalid-value or case-sensitivity behavior.

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?

The description opens with a specific verb+resource: 'Toggle a playlist mode on or off and report its new state.' This clearly distinguishes it from siblings like get_playlist or clear_playlist, though it doesn't name or contrast any sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the toggle semantics; there is no statement of when to use this versus related tools such as vlc_control or play_playlist_item, nor any preconditions (e.g. must something be playing). Adequate but with clear gaps.

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