Skip to main content
Glama

apply_elbow_edit

Applies a verified live preview as an undoable Action variant at its original frame, letting you commit reviewed Blender edits while preserving undo history.

Instructions

Apply a verified live preview as an undoable Action variant at its original frame.

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": "apply_elbow_edit"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeoutNo
candidate_idYes
expected_sessionYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already establish that this is a non-read-only, non-idempotent, non-destructive operation. The description adds useful behavioral context by saying the result is an 'undoable Action variant' at its 'original frame,' but it does not explain failure modes, session expectations, or what happens if the preview is not verified.

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 filler. Every phrase contributes to stating the operation, outcome, and undoability.

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 two required parameters and 0% schema description coverage, the description is too thin. It omits parameter semantics, prerequisites for 'verified,' and session-related behavior, even though the output schema reduces the need to explain return values.

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 compensate for all three parameters. It only indirectly hints that 'verified live preview' relates to candidate_id, and gives no meaning for expected_session or timeout, leaving required parameters unexplained.

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 uses a specific verb ('Apply') and states the resource/outcome ('a verified live preview as an undoable Action variant at its original frame'), which distinguishes it from preview and cancel operations. It does not explicitly name sibling tools, so it falls short of fully explicit sibling differentiation.

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?

The phrase 'verified live preview' implies that a preview must exist and be verified first, giving some when-to-use context. However, it does not explicitly name preview_elbow_edit or cancel_elbow_edit, nor does it state when not to use this tool or what alternatives exist.

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