vlc-mcp

Overview Schema Source Related Servers Discussions Admin

vlm

Run VLM commands to manage VLC broadcasts, or leave the command empty to list all VLM elements and return VLC's raw XML response.

Instructions

Run a VLM (VideoLAN Manager) command, or list VLM elements when command is empty.

Args: command: A VLM command such as "show", "new mybroadcast broadcast enabled", "control mybroadcast play". Leave empty to list all VLM elements. Returns VLC's raw XML response.

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

Input Schema

Name	Required	Description	Default
`command`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 12, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations at all, so the description carries the full burden. It does disclose the return format ('VLC's raw XML response') and that empty input is a read-only list, which is genuinely useful. However it never says this executes arbitrary, potentially state-changing commands against the running VLC instance, nor what happens on an invalid command or whether VLC must already 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 sentences, front-loaded with the primary action and the default case, plus a tight example list. The 'Args:' block is slightly redundant with the schema but nothing is padded.

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 needn't be re-explained, and the one parameter is covered. What is missing is the behavioral frame for an unannotated, effectively arbitrary-command tool: no note on irreversibility, side effects, or preconditions (VLC running, VLM enabled).

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 the single parameter has only a title, so the description must compensate — and it does, supplying the empty-string semantics and three concrete command shapes ('show', 'new ... broadcast enabled', 'control ... play'). It stops short of documenting argument ordering or available VLM subcommands.

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: 'Run a VLM (VideoLAN Manager) command', plus the degenerate case 'list VLM elements when command is empty'. This is distinguishable from the sibling vlc_control because it names the VLM subsystem explicitly, though it never says so outright.

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?

Gives one clear conditional (empty command = list elements) and example commands, but no guidance on when to prefer this over vlc_control or the playlist tools. The agent must infer that VLM is for broadcast/playlist-instance management rather than ordinary playback control.

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

vlm