Skip to main content
Glama

disc_list

List optical drives and detect whether each holds a DVD or Blu-ray, whether playback is supported, and inspect a specific path or disc image for playable media.

Instructions

Optical drives on this machine and whether each holds a DVD or Blu-ray, plus whether this build can play them at all. Play one with play and the drive path ("D:\"), a disc image ("film.iso"), or a folder holding VIDEO_TS / BDMV; a specific title is mpv's own syntax, "dvd://3". Each drive, and each probed path, also reports key — the identity its bookmarks and resume point are filed under, which changes when the disc does — and label, the volume name.

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

Input Schema

NameRequiredDescriptionDefault
pathNoAsk about one path instead of listing drives — reports what it is without opening it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the burden, and it does meaningful work: it discloses that the path mode 'reports what it is without opening it' (i.e., non-invasive probing), surfaces a playability-capability check, and explains that `key` is the identity used for bookmarks and resume points and changes when the disc does. It stops short of an explicit no-side-effects statement and does not describe behavior when no drives are present.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded and the density is high, but the long compound sentences with parenthetical detours are hard to parse. The aside about mpv's own title syntax ('dvd://3') belongs to `play`, not to a drive-listing tool, and consumes space without helping select or call `disc_list`.

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?

With no output schema, the description must explain returns, and it does: per-drive media type, playability, plus `key` and `label` for drives and probed paths. For a single-optional-parameter read tool this is close to complete; only edge-case behavior (empty drive list, unreadable path) is unaddressed.

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 100%, so baseline is 3, but the description adds genuine meaning: `path` switches from drive-listing to single-path interrogation, and it explains what a probed path reports (`key`, `label`). That is more than the schema's one-line description conveys.

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 opening states a concrete resource and scope: 'Optical drives on this machine and whether each holds a DVD or Blu-ray, plus whether this build can play them at all.' It also distinguishes itself from the sibling `play`. The only deduction is that the listing verb is implied rather than stated, and the second half of the description drifts into describing `play`'s input syntax rather than this tool's own job.

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

Usage Guidelines4/5

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

It explicitly routes the agent: to play a disc, use `play` with a drive path, ISO, or VIDEO_TS/BDMV folder. It also explains the one-parameter mode ('Ask about one path instead of listing drives'). There is no explicit statement of when NOT to use it, but the primary alternative and its use case are named.

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