Skip to main content
Glama
Sign In
VLC MCP Server

VLC MCP Server

by QuantumNovice
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

vlc_list_playlist

Read-onlyIdempotent

Retrieve the media items currently in VLC's playlist to inspect what is queued before controlling or changing playback.

Instructions

List media items currently 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_list_playlist"
  }
}

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 readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds the scoping detail that results reflect the current playlist state, but says nothing about ordering, empty-playlist behavior, or item fields returned.

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 front-loaded sentence with no redundant or filler wording. It states exactly what is returned and stops.

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 zero-parameter read tool with full annotation coverage, the description is adequate. However, with no output schema, an agent gets no sense of the return shape (item names, IDs, indices), which is the main remaining gap.

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 nothing to disambiguate; the baseline is 4. The description correctly implies no filtering or pagination inputs are needed.

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 gives a specific verb ('List') and resource ('media items currently in the VLC playlist'), making the read operation unmistakable. It doesn't explicitly contrast with siblings like vlc_get_status, but the playlist scope distinguishes it well enough.

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 implied: call it to inspect playlist contents before or after playback operations. There is no explicit when-to-use vs. when-not guidance and no named alternative, though 'currently in the playlist' hints at a snapshot semantics.

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