Skip to main content
Glama

get_object_detail_summary

Read-only

Inspect a Blender object by exact name to retrieve its transforms, materials, and visibility status.

Instructions

Inspect an object by exact name, including transforms, materials and visibility.

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

Input Schema

NameRequiredDescriptionDefault
nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and locality are covered by structured data. The description adds genuine value by enumerating what the inspection surfaces (transforms, materials, visibility), but says nothing about output shape, behavior on a non-existent or duplicate name, or depth of the inspection. Adequate but not rich.

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?

A single front-loaded sentence with no filler: verb, resource, lookup key, then scope of returned detail. Nothing in it is redundant or buried.

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 annotations cover the read-only profile. For a one-parameter read tool this is close to sufficient, but the missing exact-match failure semantics and the lack of differentiation from sibling object tools leave a small gap.

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 single parameter is documented only as "Name", so the description must carry the semantics. It does add the meaningful qualifier "exact", signaling exact-match rather than fuzzy/partial lookup, but leaves case sensitivity and duplicate-name resolution unstated.

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 pairs a specific verb ("Inspect") with a specific resource ("an object") and names the lookup key ("exact name"), plus the categories of detail returned: transforms, materials, visibility. It does not distinguish itself from nearby siblings such as get_objects_summary or the jump_to_view3d_object_* tools, so an agent must infer the boundary.

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 explicit statement of when to use this versus the summary/jump siblings, and no when-not guidance or prerequisites. The only usable cue is the implicit "inspect one object" framing and the "exact name" constraint, which is thin guidance for choosing among several object-oriented tools.

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