Skip to main content
Glama

grade_versions

Manage color grade versions for a timeline item by listing local or remote versions and adding, loading, renaming, or deleting them as needed.

Instructions

Color grade versions of a timeline item: list (local and remote), add, load, rename, delete. remote=true works on remote versions.

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": {
      "item": "<item>",
      "action": "<action>"
    },
    "name": "grade_versions"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYes
nameNo
actionYes
remoteNo
new_nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations declare destructiveHint=false, yet the description advertises a 'delete' action — a removal operation the annotation says the tool does not perform. Beyond that, nothing is disclosed about whether 'load' overwrites the item's current grade, whether deletes are recoverable, or what permissions are needed.

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?

Two short sentences, action list front-loaded, no filler. The brevity is appropriate even though it is achieved partly by omitting necessary detail.

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?

A five-parameter, five-action mutation tool with no output schema and no annotated safety detail needs per-action parameter mapping and outcome description; neither is present. An agent cannot tell from the definition what a successful call returns or which optional fields are required for each action.

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

Parameters2/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 parameter meaning, and it explains only 'remote'. It gives no mapping of which parameters each action needs (e.g., name for add/load, new_name for rename) and no meaning for 'item', 'name', or 'new_name'.

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?

Names a specific verb set and resource: version operations (list, add, load, rename, delete) on the color grade of a timeline item. The action enumeration lets an agent distinguish it from apply_grade or copy_grade, though neither sibling is named explicitly.

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 only guidance is 'remote=true works on remote versions', which is a parameter note rather than a when-to-use rule. There is no indication of when to pick grade_versions over apply_grade/copy_grade, nor which action suits which situation.

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