Skip to main content
Glama

grade_drx

Apply a saved .drx grade to clips with optional keyframe modes: none, source timecode, or start frames.

Instructions

Apply a saved grade (.drx still file) to clips. mode: none (no keyframes) | source_tc | start_frames.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "clips": "<clips>",
      "path": "<path>"
    },
    "name": "grade_drx"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNonone
pathYes
clipsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does not say whether applying a grade overwrites existing clip grades, whether the operation is reversible, or what permissions or media state are required. Only the 'mode' label list hints at behavior, without explaining consequences.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is two short fragments, front-loaded with the core action and then the mode options. Nothing is padded, though the pipe-delimited mode list is terse to the point of being cryptic.

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?

For a mutation tool with zero annotation coverage, no output schema, and three undocumented parameters, this is thin. The agent lacks the mode-value meanings, the expected shape of 'clips', and any statement of what happens to pre-existing grade data on the target clips.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/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 compensate, and it partially does: it identifies 'path' as a .drx still file and lists the three 'mode' values, noting 'none' means no keyframes. However, 'source_tc' and 'start_frames' are opaque labels with no explanation, and the 'clips' parameter is not addressed at all.

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 gives a specific verb and resource: 'Apply a saved grade (.drx still file) to clips.' The file-format detail distinguishes it from siblings like grade_cdl and grade_lut, which presumably take other input types. It stops short of naming an explicit alternative, but the .drx scope is concrete enough to select on.

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 statement of when to use this versus grade_cdl, grade_look, or grade_copy. The .drx format implies the input precondition, but the agent must infer that, and no exclusions or prerequisites are given.

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