Skip to main content
Glama

jump_to_view3d_object_data_by_name

Locate a specific Blender 3D object by datablock name and frame it in the viewport for inspection.

Instructions

Frame the object that uses a datablock with the given name.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
allow_editsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations declare readOnlyHint=false, so this tool can mutate state, yet the description says nothing about what gets changed. The 'allow_edits' parameter clearly gates some write behavior, but the description never explains it, leaving the mutation profile opaque.

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?

A single front-loaded sentence with no filler. It is lean to a fault — the brevity comes at the cost of the missing behavioral and parameter detail rather than through efficient compression.

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?

An output schema exists so return values need no explanation, but for a non-readonly viewport-navigation tool with a mutation-gating flag, the definition omits the behavior an agent needs to call it safely. The core gap is 'allow_edits' and the write side effects it enables.

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 coverage is 0% with two parameters. The description clarifies that 'name' refers to a datablock name rather than an object name, which is useful, but 'allow_edits' is completely undocumented in both schema and description despite being the safety-relevant flag.

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?

States a concrete verb ('Frame') and resource ('the object that uses a datablock with the given name'), and implicitly distinguishes itself from jump_to_view3d_object_by_name by keying on datablock name rather than object name. The differentiation is inferable but never stated explicitly, so an agent must reason about it.

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?

No when-to-use guidance, no mention of when to prefer the sibling jump_to_view3d_object_by_name, and no prerequisites. The agent must infer selection from the name alone.

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