Skip to main content
Glama

list_databases

Read-only

Lists available DaVinci Resolve project databases and identifies the current database, helping agents choose or confirm where projects are stored.

Instructions

Available project databases and the current one.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the bar is lower. The description adds one useful behavioral fact beyond the annotations: the result also surfaces the currently active database. It says nothing about whether the list is local, cloud, or cached, or whether the 'current' marker can be absent.

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?

Only eight words, so nothing is wasted, but the fragment structure means the resource is not front-loaded by a verb and the key fact (which database is current) is tacked on with 'and'. Brevity here reads as under-specification rather than tight writing.

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 zero-param read with readOnlyHint and no output schema, the description should at least characterize what is returned, and it partially does by naming databases plus the current one. It leaves open the scope of enumeration and the shape of the 'current' indicator, which is the main gap for an otherwise simple tool.

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 schema imposes no semantic burden and the baseline is 4. There is nothing about parameters the description could add.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Available project databases and the current one" identifies the resource and hints at the return shape, but it is a noun fragment with no verb, and it never distinguishes this list from siblings like list_projects or list_volumes. An agent can guess it enumerates databases, but not the scope (all databases vs. only those of the current project).

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 when-to-use guidance, no prerequisites, and no named alternative. The agent is left to infer that this is the discovery call to make before any database-scoped operation.

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