Skip to main content
Glama
Aedelon

davinci-mcp

by Aedelon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Describe Action

describe_action
Read-onlyIdempotent

Retrieves compact parameter schemas and flags for one or more DaVinci Resolve actions, so you can validate inputs and construct calls without guessing signatures.

Instructions

Parameter schemas (compact) of one or several actions, with their flags.

With only tool, lists that tool's actions and their signatures.

Input Schema

NameRequiredDescriptionDefault
toolNoTool name, e.g. 'timeline_write'.
actionNoop.action, e.g. 'append_clips'.
actionsNoSeveral at once, as 'tool.action' (e.g. ['color_write.set_cdl', 'gallery_write.grab_still']): one call instead of one per action.
with_resultNoAlso return result schemas.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, closed-world behavior. The description adds useful context about the returned data: compact parameter schemas, action flags, and the tool-only listing behavior. It leaves 'flags' undefined, but the added context is meaningful beyond annotations.

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 two compact sentences with no filler. The core function is front-loaded, followed immediately by the tool-only listing behavior.

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 read-only introspection tool with full schema descriptions and annotations, the description covers the essential behavior and output nature. It is nearly complete, though it could briefly clarify what 'flags' means and whether `with_result` changes the response shape.

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 100%, so the schema already documents all four parameters in detail. The description still adds semantic value by explaining the special behavior when only `tool` is supplied. It does not further clarify precedence among `action`, `actions`, and `with_result`.

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 states a specific resource and operation: it returns compact parameter schemas for one or several actions, including their flags. It also clarifies the tool-only listing mode. It does not explicitly distinguish itself from execution-oriented sibling tools, but the introspection purpose is clear.

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?

The description implies discovery usage by explaining that providing only `tool` lists that tool's actions and signatures. However, it does not say when to use this instead of `search_api` or before invoking an action tool, nor does it state when not to use it.

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