Skip to main content
Glama
Sign In
vlc-mcp

vlc-mcp

by jaseonline
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_volume

Retrieve the current VLC volume level as a percentage to check or confirm playback volume before adjusting it.

Instructions

Get the current volume level of VLC (as a percentage).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden and it only covers the read nature of the call. It says nothing about behavior when VLC is unreachable, what happens if no media is loaded, or whether the value reflects a per-session or global setting – all plausible failure modes for a player-volume query.

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 verb, resource, and unit front-loaded, and no filler. Nothing could be removed without losing information.

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?

An output schema exists, so the description is not obliged to describe the return value, and for a zero-argument getter the remaining requirement is small. The only meaningful omission is error/unavailable-state behavior, which is minor given the tool's simplicity.

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 the baseline is 4; there are no arguments whose meaning could be under-specified. The only semantic content needed, that the value is a percentage, is already present in the description.

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 (get) and resource (volume level) with the unit made explicit ('as a percentage'), and the word 'current' clarifies it reads live state rather than a stored value. It does not name the sibling tools it is distinct from, but the get/set/adjust naming pattern makes read-vs-write unambiguous.

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 by the 'get' verb – an agent can infer this is the read path and that set_volume or adjust_volume handle modification, but the description never says so or states any precondition (e.g. VLC must be running). Adequate but leaves the when-to-use choice to inference.

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