Skip to main content
Glama
Sign In
resolve-mcp

resolve-mcp

by irstone-source
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

timeline_settings_get

Retrieve timeline settings from DaVinci Resolve, optionally filtering by setting name or project handle.

Instructions

Read timeline settings. Returns all of them when setting is omitted.

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

Input Schema

NameRequiredDescriptionDefault
settingNo
name_or_handleNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Without annotations, the description carries full burden. It discloses that the tool is read-only and that omitting the setting parameter returns all settings. However, it does not cover other behavioral aspects like authentication or side effects, which are minimal for a read tool.

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?

The description is extremely concise with two sentences, zero wasted words, and front-loads the main purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description does not specify the return format. It also fails to explain the 'name_or_handle' parameter contextually. For a getter with two parameters, more detail is needed to be fully complete.

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?

Schema description coverage is 0%, so description must add meaning. It partially explains the 'setting' parameter by saying 'Returns all of them when setting is omitted,' but the 'name_or_handle' parameter is completely undocumented, leaving a significant gap.

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

Purpose5/5

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

The description clearly states it reads timeline settings, providing a specific verb and resource. It also clarifies behavior when the setting parameter is omitted. The name differentiates it from sibling tools like 'timeline_settings_set' which is for writing.

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?

No explicit guidance on when to use this tool versus alternatives. While sibling tools like 'timeline_settings_set' imply modification, the description does not mention usage context or exclusions.

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