Skip to main content
Glama
Sign In
VLC MCP Server

VLC MCP Server

by QuantumNovice
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

vlc_play

Starts or resumes VLC playback, optionally playing a specific playlist item by its numeric ID. Use it to begin media or continue the current selection.

Instructions

Start or resume VLC playback. Optionally play a playlist item by its numeric ID.

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

Input Schema

NameRequiredDescriptionDefault
item_idNoVLC playlist item ID. Omit to resume or start the current selection.

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 readOnlyHint=false, destructiveHint=false, and non-idempotent, so the safety profile is covered. The description adds the useful 'resume' nuance (continues rather than restarts) but says nothing about failure modes, missing selection, or whether a session must be running.

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 primary action, with the optional targeting mode second. No filler or redundant phrasing.

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-optional-parameter transport control with no output schema, the definition covers the core action and the meaning of omission. Only prerequisite and error-state context is missing, which is minor 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?

Schema coverage is 100% and the schema description already explains item_id and the omit-to-resume behavior. The description's 'play a playlist item by its numeric ID' largely restates the schema, adding little new meaning.

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 and resource: 'Start or resume VLC playback', with an optional item-targeting mode. It implicitly separates itself from transport siblings like vlc_pause and vlc_stop, but never names them or states the boundary 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?

The clause 'Omit to resume or start the current selection' is useful guidance for the parameter, but there is no explicit when-to-use versus alternatives (vlc_pause, vlc_next, vlc_add_media) and no stated prerequisites such as an active VLC connection.

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