Skip to main content
Glama

list_api_methods

Read-only

Lists DaVinci Resolve 21.1 API classes or, given a class name, every method with its signature and documentation to help you discover scripting calls.

Instructions

Every method of an API class with signature and documentation (Resolve 21.1 stubs). Without class_name, lists the classes.

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_api_methods"
  }
}

Input Schema

NameRequiredDescriptionDefault
class_nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/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. The description adds a useful caveat that results are 'Resolve 21.1 stubs', warning that coverage may be incomplete, but it says nothing about output volume, pagination, or how large class listings can get.

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?

Two compact sentences, the primary behavior first and the parameter-dependent fallback second, with no redundant restatement of the name or schema.

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 single optional-parameter read tool with no output schema, the description states both modes and roughly what is returned (signatures and documentation). Only the class_name value format and result size are unaddressed.

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 description coverage is 0%, so the description must carry the meaning of class_name, and it does: supplying it switches to method listing, omitting it lists classes. That is exactly the semantic distinction the schema does not convey, though the expected string format of class_name is not shown.

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 names a specific verb and resource ('Every method of an API class with signature and documentation') and states the fallback behavior of listing classes when no class is given. An agent can distinguish it from call_api or get_api_docs, though it never explicitly says so.

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?

Usage is only implied through the two-mode sentence: pass class_name to enumerate methods, omit it to enumerate classes. There is no explicit guidance on when to prefer this over search_api or get_api_docs, so routing between siblings is left to inference.

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