Skip to main content
Glama

reveal_in_storage

Locate a specific file or folder by showing it in DaVinci Resolve's Media page storage browser.

Instructions

Show a file or folder in the Media page's storage browser.

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

Input Schema

NameRequiredDescriptionDefault
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

The annotations already state readOnlyHint=false, destructiveHint=false, and openWorldHint=false, and the description adds nothing beyond them. It does not say whether revealing changes the browser's current location or selection, what happens when the path does not exist, or whether the storage panel must already be open. For a non-read-only UI-state action, that is a real gap.

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?

It is one short, front-loaded sentence with no filler, so it is easy to scan. The brevity borders on under-specification rather than waste, but nothing in the text is removable.

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?

This is a simple one-parameter tool with no output schema and with annotations that already carry the safety profile, so it needs less prose than a complex tool does. Still, the only parameter's format is completely undocumented and the observable effect of the call is unstated, leaving an agent to guess at both.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter 'path' has 0% schema description coverage, and the description does not compensate at all. It never says whether the path is absolute or relative, whether it is a filesystem path or a Media-page virtual path, whether trailing slashes matter, or how to address a folder versus a file.

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 gives a specific verb and resource: reveal a file or folder inside the Media page's storage browser. That is clearly more than a restatement of the name. It stops short of 5 because it never distinguishes this action from the sibling browse_storage, so an agent must infer which one navigates versus which one reveals.

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 guidance, no exclusion conditions, and no mention of an alternative such as browse_storage. The context (a storage browser on the Media page) only weakly implies that this tool is for locating an existing path in the UI; an agent gets no help deciding whether to use this tool or browse instead.

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