Skip to main content
Glama

preview_elbow_edit

Read-only

Preview FK elbow adjustments while keeping the planted hand’s pose fixed, then stage candidate keys to check surrounding motion before restoring the original Action.

Instructions

Preview an FK elbow move while preserving the planted hand's pose.

Pass a v1 rig profile and the current session ID for a live candidate. Headless previews are available with blend_file. Supply a signed swivel or world elbow target, or omit both to improve wrist alignment within the profile's limit. The preview stages the intended keys and checks the surrounding motion before restoring the original 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": {
      "profile": "<profile>"
    },
    "name": "preview_elbow_edit"
  }
}

Input Schema

NameRequiredDescriptionDefault
frameNo
viewsNo
profileYes
timeoutNo
blend_fileNo
elbow_targetNo
swivel_degreesNo
expected_sessionNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, but the description reveals something the annotation cannot: the preview temporarily stages intended keys, checks surrounding motion, then restores the original Action, and it flags a session handshake via the current session ID. It does not cover failure/timeout behavior or whether staged keys carry over to an apply call.

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?

Front-loaded with purpose, then mode selection, then target choice, then the side-effect note — a sensible ordering. Five sentences of dense domain jargon, but each carries distinct operational information; only 'improve wrist alignment within the profile's limit' verges on padding.

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?

An output schema exists, so return values need no explanation, and the non-destructive preview semantics are well covered. However, for an 8-parameter tool with a free-form nested profile object at 0% schema coverage, the description leaves the profile contract, the frame selection, and the session lifecycle underspecified.

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 coverage is 0%, and the description only adds meaning for four of eight parameters (profile as a 'v1 rig profile', expected_session as the current session ID, blend_file for headless mode, and the signed swivel / world-space elbow target pair with their omit-to-default behavior). It says nothing about frame, views, or timeout, and leaves the nested profile object's shape undefined.

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?

States a specific verb and resource ('Preview an FK elbow move') plus the defining constraint ('preserving the planted hand's pose'), and the closing sentence separates it from a commit-style sibling by noting it restores the original Action. An agent can distinguish this from apply_elbow_edit purely from the text.

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?

Gives concrete conditional routing: session ID for a live candidate, blend_file for headless previews, and either a signed swivel or world elbow target (or neither, to let wrist alignment be improved). It stops short of explicitly naming when to prefer apply_elbow_edit or cancel_elbow_edit over this, so alternatives are implied rather than stated.

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