Skip to main content
Glama

media_storage

Browse disks as DaVinci Resolve sees them: list mounted volumes, folder contents, and media files, with image sequences consolidated for easier selection.

Instructions

Browse disks as Resolve sees them: no path → mounted volumes; a folder → its sub-folders and media files (image sequences are consolidated).

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

Input Schema

NameRequiredDescriptionDefault
pathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are present, so the description carries the full load. It does disclose the mode switch and a non-obvious behavior (image sequences are consolidated), and 'Browse' implies a read-only operation, but it never confirms non-destructiveness, permission requirements, or volume-visibility caveats in Resolve.

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?

One sentence, no filler, and the default behavior (no path) is front-loaded ahead of the folder case. The arrow notation makes the two branches scannable.

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 one-parameter read tool with no output schema, the description covers all three things an agent needs: what is enumerated, how the argument changes the result, and one important normalization quirk. Missing only confirmation of read-only status and path format conventions.

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% for the single 'path' parameter, and the description compensates well by defining exactly what null means (mounted volumes) and what a folder argument yields (sub-folders and media files). It stops short of specifying path format (absolute vs relative, separators) which the schema also omits.

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?

Clear verb ('Browse') plus a specific resource ('disks as Resolve sees them'), and the dual-mode behavior is stated. It does not explicitly contrast itself with nearby siblings like media_pool or media_import, so an agent must infer that this is filesystem-level browsing rather than project-bin browsing.

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 rather than stated: passing no path to enumerate mounts versus passing a folder to enumerate its contents tells the agent how to steer the call, but there is no explicit when-to-use/when-not guidance and no named alternative for project-media lookup.

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