Skip to main content
Glama

jump_to_view3d_object_by_name

Frames a named object in the current 3D viewport and reveals it when edits are allowed, helping you locate scene objects by name.

Instructions

Frame the named object in the current 3D viewport, revealing it if allowed.

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_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

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, so the safety profile is partly covered. The description adds real context by implying the call can change visibility state ("revealing it") and that this is gated ("if allowed"), but it never explains what "allowed" depends on or what happens if the object is already hidden and edits are disallowed. No contradiction with annotations.

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 padding; the core action comes first. Its brevity borders on under-specification rather than waste, so it is efficient but thin.

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 not be described, and the tool has only two parameters. Still, for a tool whose behavior differs based on allow_edits and on whether the object is hidden, the definition omits the outcomes an agent needs to predict consequences.

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 carry parameter meaning. It only loosely maps to both parameters: "named object" for name and "if allowed" for allow_edits. It never states what allow_edits=true unlocks or what the behavior is when it is false (the default), leaving the key branching semantics undocumented.

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?

"Frame the named object in the current 3D viewport" gives a specific verb (frame) and resource (named object), so an agent knows the primary effect. However, there is a near-identical sibling (jump_to_view3d_object_data_by_name) and the description does nothing to distinguish the two, leaving the scoping of "frame" versus "data" ambiguous.

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 when-to-use guidance, no exclusions, and no mention of when the sibling jump_to_view3d_object_data_by_name would be the better pick. The clause "revealing it if allowed" hints at a precondition but never states it (e.g. hidden objects, edit permissions).

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