Skip to main content
Glama

cancel_elbow_edit

Discards an unused live preview without editing the pose or the Action, letting you back out of an elbow edit cleanly by candidate ID and session.

Instructions

Discard an unused live preview without editing the pose or the Action.

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": {
      "candidate_id": "<candidate_id>",
      "expected_session": "<expected_session>"
    },
    "name": "cancel_elbow_edit"
  }
}

Input Schema

NameRequiredDescriptionDefault
candidate_idYes
expected_sessionYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false. The description adds useful context that canceling discards a live preview without editing the pose or Action, but it does not explain session validation, failure cases, or what state changes occur beyond that.

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, front-loaded sentence with no redundant wording. It communicates the core action and its main non-effect efficiently.

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 purpose and non-destructive behavior are clear, and an output schema exists, so return values need not be described. However, with two required parameters and no schema descriptions, the definition is not complete enough to reliably guide invocation.

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?

Both required parameters, candidate_id and expected_session, have 0% schema description coverage, and the description does not explain either one. The phrase 'live preview' weakly hints that candidate_id identifies a preview candidate, but expected_session remains entirely undocumented.

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 states a specific verb and resource: 'Discard' a 'live preview.' It also distinguishes the operation from applying or editing by saying it happens 'without editing the pose or the Action.'

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'Discard an unused live preview' gives clear context for when to use the tool: abandoning a preview rather than applying it. However, it does not explicitly name alternatives like apply_elbow_edit or preview_elbow_edit, nor does it state prerequisites or failure conditions.

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