Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

get_scene_summary

Retrieve high-level metadata from the active Blender scene—name, frame range, FPS, unit system, object totals by type, active camera/object—to inspect and verify the scene.

Instructions

Retrieve high-level summary metadata about the active Blender scene: scene name, current frame, frame range, FPS, unit system, total object count, breakdown of objects by type (mesh, camera, light, armature, etc.), active camera, and active object.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_scene_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
include_collectionsNoWhether to include a list of top-level collection names.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; 'retrieve' does signal a read-only operation, and the field enumeration gives a useful picture of what comes back. However, it says nothing about failure modes (no active scene), cost/latency, or whether the call has any side effects, which leaves real behavioral gaps for an unannotated tool.

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?

One sentence, front-loaded with the verb and resource, and the trailing list is entirely load-bearing because it documents return fields that have no output schema. No filler, hedging, or restatement of the tool name.

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?

With no output schema, the description's field list is exactly the right compensation and covers the main return payload thoroughly. The remaining gap is minor: it doesn't explain how include_collections alters the response or what happens when no scene is active.

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?

The single parameter include_collections is fully documented in the schema (100% coverage) with its default, and the description never mentions it. Per the high-coverage baseline this is adequate, but the description adds no meaning beyond the schema – notably it doesn't say that collection names are what the flag toggles in the returned payload.

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 specific verb (retrieve) and resource (high-level summary metadata about the active Blender scene) and then enumerates exactly which fields come back (name, frame, range, FPS, unit system, object counts, active camera/object). This makes the tool's scope unmistakable relative to a per-object tool like get_object_details, though it never names an alternative explicitly.

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 is only implied by the phrase 'high-level summary' – an agent can infer this is the orientation/overview call before drilling into details. There is no explicit when-to-use statement, no when-not-to-use, and no mention of prerequisites such as requiring an active scene or live Blender connection.

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

Deploy Server

Other Tools