Skip to main content
Glama

jump_to_motion_witness

Idempotent

Jump from the current live Blender scene to a saved evidence bookmark and frame the witness for inspection.

Instructions

Jump to an evidence bookmark from the current live Blender scene and frame the witness.

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": {
      "bookmark": "<bookmark>"
    },
    "name": "jump_to_motion_witness"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewNofront
bookmarkYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

B3/5.0
Behavior3/5

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

The annotations already declare the operation non-destructive, idempotent, and confined to the local Blender environment. The description adds that it acts on the current live scene and frames the witness, but it does not explain whether camera, selection, or viewport state changes, nor what happens if the bookmark is missing.

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 definition is a single compact sentence with the action front-loaded and no redundant wording. Every phrase contributes either scope or behavior.

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?

The tool has a required nested bookmark object and an undocumented view parameter, making the short description insufficient for correct invocation. The output schema exists, so return values need not be explained, but the input-side gaps are substantial.

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 explain the parameters. It mentions the bookmark only as an 'evidence bookmark' and never describes its structure, and it does not mention the 'view' parameter or its default value at all.

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 gives a specific verb and target: jump to an evidence bookmark and frame the witness in the current live Blender scene. It is clearer than a generic navigation tool, though the jargon terms 'evidence bookmark' and 'witness' are not defined and no sibling tool is explicitly contrasted.

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?

There is no guidance on when to use this tool versus alternatives such as compare_motion_reviews or review_motion_contacts. The phrase 'from the current live Blender scene' implies context, but it does not state prerequisites, exclusions, or alternative selection criteria.

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