Skip to main content
Glama

grade_reset

Resets all grades on specified clips' node graphs or on timeline/group pre/post grades, clearing color corrections so you can start fresh.

Instructions

Reset all grades on the clips' node graphs (or 'timeline' / 'group::pre|post').

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>"
    },
    "name": "grade_reset"
  }
}

Input Schema

NameRequiredDescriptionDefault
clipsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It does usefully disclose the scope of destruction ('all grades' on the target node graphs), which is the key risk fact for an agent. It omits reversibility, permission requirements, and whether the reset is applied atomically across multiple clips.

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?

A single front-loaded sentence with the operation and its scope stated first, followed by the target-variant parenthetical. No filler and nothing to trim.

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?

For a one-parameter, no-output-schema, annotation-free mutation tool, the description covers the what and the target forms adequately. It is missing the behavioral envelope an agent needs before invoking a destructive reset — reversibility and required permissions — so it is minimum viable rather than complete.

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% — the single required 'clips' parameter has only a title. The description partially compensates by revealing that the target may be a clip node graph, the literal 'timeline', or a 'group:<name>:pre|post' form, which is real syntax detail not in the schema. It does not explain the expected type/shape for the clips argument when multiple clips are passed.

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 ('Reset all grades on the clips' node graphs'), which clearly contrasts with the sibling grade_* tools that apply or copy grades (grade_cdl, grade_lut, grade_copy). It stops short of naming an alternative explicitly, but the reset-vs-apply distinction is inferable from the verb and the siblings' names.

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: the verb 'reset' signals this is the tool to remove existing grades rather than set them. There is no explicit statement of when to prefer this over grade_copy or grade_cdl, no preconditions, and no warning about 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.