Skip to main content
Glama

scene

Read-only

Inspect Blender object hierarchy, topology, materials, and file settings via read-only reports to verify edits and diagnose issues.

Instructions

Scene report (read-only): the header has object/type counts, active, selected, mode; then fields per object (default: top-level objects, location+size+children+hidden). fields: location, size (world box including children), ground (ok/floating/below), rotation, scale, parent, children, hidden, details (faces/tris/verts, bones, light), materials, modifiers, animation; topology (quads/tris/ngons, boundary and non-manifold edges, loose vertices, poles); weights (vertices a deform bone does not move, bones without a vertex group); gta (Sollumz: UVMap 0, Color 1, sz_lods, shader, missing textures, unapplied transforms, .001 suffix); settings (file, engine, frames, resolution, camera, HDRI, units). Groups: placement, contents, health, all. root='Name': that object's hierarchy; query='text': the objects with it in their name; limit at most 200 lines.

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

Input Schema

NameRequiredDescriptionDefault
appYes
rootNo
limitNo
queryNo
fieldsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description reinforces the read-only nature up front. It adds genuinely behavioral detail beyond the annotations: the default field set is top-level objects with location+size+children+hidden, 'size' is a world box including children, and output is capped at 200 lines. That is useful context an agent could not get from annotations alone.

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?

It is dense but front-loaded, leading with purpose and read-only status before the field catalog. The semicolon-separated clause structure keeps a long enumeration navigable, and nearly every item maps to a real parameter value. The prose is comma-spliced in places, but with 0% schema coverage the enumeration earns its length.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so the description need not explain return formatting, and it correctly focuses on selection semantics instead. Given five parameters and a rich report surface, the description is close to complete; the omissions are the unexplained 'app' parameter and any hint about cost or how to narrow fields for large scenes.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden and mostly succeeds: it defines root, query, limit, and comprehensively enumerates the accepted values for fields (individual field names plus the placement/contents/health/all groups). The one required parameter, 'app', is never explained anywhere, which is the notable gap keeping this below a 5.

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 opens with a specific verb+resource pairing, 'Scene report (read-only)', and immediately enumerates what the report contains (counts, per-object fields, topology, weights, gta checks, settings), so an agent knows exactly what it gets back. It does not explicitly distinguish itself from siblings like 'view' or 'status', which leaves a small ambiguity, but the enumeration makes the tool's function unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage of the selector parameters is well explained: root='Name' returns that object's hierarchy, query='text' filters by name, and limit caps output at 200 lines. However, there is no statement of when to prefer this tool over alternatives, no prerequisites, and no guidance on which 'group' to choose for a given intent. Usage is implied by the parameter semantics rather than stated as decision guidance.

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