Skip to main content
Glama

inspect_scene

Retrieve Blender version, current frame, and object transforms from a session, with pagination to page through large scenes.

Instructions

Inspect Blender version, frame and object transforms with pagination.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
session_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. 'Inspect' implies a read-only operation and 'with pagination' discloses paged results, but nothing is said about whether a session must be active, whether the call is cheap or heavy, or how truncated results behave.

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 tight sentence with the scope front-loaded and no filler. It is appropriately brief, though brevity here edges into under-specification rather than economy.

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?

With three undocumented parameters, no annotations, and no output schema, the description should say more: what the response looks like, how transforms are represented, and what session_id refers to. As written, an agent knows roughly what the tool does but not how to call it correctly.

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 compensate and does not. It implies limit/offset through 'pagination' but never explains them, and the required session_id parameter — the most important one — is not mentioned 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 (inspect) plus concrete resources: Blender version, current frame, and object transforms, and notes pagination. It does not differentiate from siblings such as inspect_object or inspect_nodes, which likely overlap in scope, so it falls short of a 5.

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 inspect_object, inspect_nodes, inspect_dependencies, or get_environment. The agent must infer from the name alone that this is the broad scene-level read.

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