Skip to main content
Glama
Sign In
VLC MCP Server

VLC MCP Server

by QuantumNovice
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

vlc_add_media

Adds a local file path or supported media URL to the VLC playlist so you can queue media for playback.

Instructions

Add media to the VLC playlist. Accepts a local path or media URL supported by VLC.

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": {
      "input": "<input>"
    },
    "name": "vlc_add_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYesLocal media path or media URL.

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, idempotentHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the useful detail that input may be a local path or a VLC-supported URL, but says nothing about whether the item is appended to the queue, auto-played, or duplicated on repeat calls.

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 short sentences with no filler, and the core action is front-loaded ahead of the input-domain detail. Nothing is redundant or padded.

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-parameter mutation tool with a fully documented schema and complete annotations, the definition covers the essentials. The remaining gap is what happens on success (whether playback starts or the item merely queues), which matters slightly even without an output schema.

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 single parameter already carries the description 'Local media path or media URL.' The tool description restates that same domain without adding format examples, URL scheme constraints, or behavior for unsupported inputs.

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 ('Add') and resource ('media to the VLC playlist'), and the second sentence narrows the accepted input domain. An agent can distinguish this from playback-control siblings like vlc_play or vlc_pause without opening any schema.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no statement of prerequisites (e.g. whether the media must be added before vlc_play), and no mention of alternatives or exclusions. The sequencing role is only implied by the sibling names.

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