Skip to main content
Glama
Sign In
VLC MCP Server

VLC MCP Server

by QuantumNovice
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

vlc_previous

Skip back to the previous item in a VLC playlist to return to the prior track or video when controlling local VLC playback.

Instructions

Return to the previous item in the VLC playlist.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare this is not read-only and not idempotent, so the agent knows it mutates playback state; the description adds that the mutation is scoped to the playlist queue. It does not disclose whether playback resumes/starts, whether it wraps at the start of the playlist, or whether it only moves a cursor versus actually playing. Given annotation coverage, a 3 is appropriate.

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?

A single short sentence with the action and scope front-loaded and zero filler. Nothing in it is redundant.

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 trivial zero-parameter navigation tool with annotations covering the safety profile and no output schema, the description is close to sufficient. However, the outcome of the call (does playback begin, what happens at the playlist boundary) is left ambiguous, which is the one thing an agent could actually get wrong here.

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?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description does not introduce any confusing argument-like language.

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?

"Return to the previous item in the VLC playlist" pairs a specific verb (return to previous item) with a specific resource (the VLC playlist), which makes it naturally distinguishable from the sibling vlc_next. It stops short of explicitly naming that sibling, so it is clear but not maximally differentiated.

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: an agent can infer this applies when stepping backward through the playlist queue, but the description gives no conditions, no boundary behavior (what happens at the first item), and no prerequisites such as an active playlist or playing session. It does not name alternatives, though the sibling name vlc_next makes the split obvious.

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