Skip to main content
Glama

browse_storage

Read-only

Browse sub-folders and media files at an absolute path as DaVinci Resolve's Media Storage sees them, with image sequences consolidated into single entries.

Instructions

Sub-folders and media files of an absolute path as Media Storage sees it (image sequences are consolidated into single entries).

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": {
      "path": "<path>"
    },
    "name": "browse_storage"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

The readOnlyHint and openWorldHint=false annotations already establish that this is a safe, closed-world read. The description adds one genuine behavioral detail beyond them: image sequences are consolidated into single entries, which materially affects how results should be interpreted. It is silent on recursion depth, pagination, and error behavior for invalid paths.

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

Conciseness4/5

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

One sentence, front-loaded with what is returned, with no filler. It reads as a noun phrase rather than a verb-led statement, which slightly weakens immediate scannability, but nothing is wasted.

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?

For a one-parameter read-only tool with no output schema, the description covers the essential return contents and the image-sequence consolidation rule. It omits whether listing is recursive or single-level, and how paths outside Media Storage's scope are handled, which are relevant for calling it correctly.

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 0%, so the description carries the burden for the single 'path' parameter. It does communicate the important constraint that the path must be absolute and that it lives in Media Storage's namespace, but it gives no examples or format conventions, leaving meaningful ambiguity about valid path syntax.

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 description names the concrete resource returned (sub-folders and media files) and the scoping qualifier 'as Media Storage sees it,' which distinguishes a logical storage view from a raw filesystem listing. It does not, however, contrast itself with the sibling reveal_in_storage, leaving the agent to infer the difference.

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 or when-not-to-use guidance, and no mention of the obvious alternative (reveal_in_storage) or of prerequisites such as needing a valid absolute path. Navigation intent is only implied by the tool name.

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