Skip to main content
Glama
hoyt-harness

DaVinci MCP Professional

by hoyt-harness
OverviewSchemaRelated ServersScoreDiscussions
Python

get_version

Retrieve the version of the installed DaVinci Resolve software. This tool returns the version number for compatibility checks and troubleshooting.

Instructions

Get DaVinci Resolve version information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/davinci_mcp/tools/__init__.py:12-16 (registration)
    MCP tool registration: defines the 'get_version' tool with its name, description, and empty input schema.
    types.Tool(
    name="get_version",
    description="Get DaVinci Resolve version information",
    inputSchema={"type": "object", "properties": {}, "required": []},
),

Tool Definition Quality

A3.5/5.0
Behavior2/5

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

With no annotations, the description does not disclose any behavioral traits such as side effects, authentication needs, or limitations. It simply restates the name, adding no extra insight beyond what the tool name provides.

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 a single sentence with no extraneous words. It is front-loaded and efficient, earning its place without any waste.

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?

The tool is simple with no parameters, but the description fails to mention the return format or any error conditions. Since there is no output schema, this information would be helpful. However, the description still provides the core purpose adequately, earning a mid-range score.

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 input schema has zero parameters and 100% description coverage (trivially). The description does not need to elaborate on parameters, and the baseline score of 4 is appropriate for a parameterless tool.

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 the verb 'Get' and the resource 'DaVinci Resolve version information', making the tool's purpose immediately obvious. It effectively distinguishes itself from sibling tools which deal with projects, timelines, media, etc.

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?

The description provides no guidance on when to use this tool versus alternatives or any context about prerequisites. While the tool is straightforward, the lack of any usage hints is a missed opportunity.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/hoyt-harness/davinci-mcp-professional'

If you have feedback or need assistance with the MCP directory API, please join our Discord server