Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

list_objects

Inspect objects in the active Blender scene with filters, pagination, and hierarchy details, returning names, types, collections, visibility, parents, and child counts.

Instructions

List objects in the active scene with filtering, pagination, and structural hierarchy. Returns object names, types, associated collections, visibility, parent, and child count.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of objects to return (1 to 1000).
offsetNoNumber of objects to skip for pagination.
object_typeNoOptional object type filter (e.g. 'MESH', 'CAMERA', 'LIGHT', 'ARMATURE', 'EMPTY', 'CURVE').
include_hiddenNoWhether to include hidden or disabled objects.
collection_nameNoOptional collection name filter. Only objects linked to this collection are returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it does meaningful work: it states the returned fields (names, types, collections, visibility, parent, child count) and calls out pagination and hierarchy behavior, implying a non-mutating read. It leaves out any note on performance or scene-state preconditions, keeping it just under full marks.

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?

Two sentences, front-loaded with the core action and scope, then the return shape. Every clause carries information and there is no redundant 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 five fully documented optional parameters and no output schema, the description supplies the return-field summary that is otherwise missing. The one gap is that "structural hierarchy" is left vague as to how parent/child relationships are expressed in the response.

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 description coverage is 100%, so every parameter is already documented in the schema, and the baseline is 3. The description gestures at the same dimensions (filtering, pagination) but adds no syntax or semantics beyond what the schema already states.

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 names a specific verb and resource ("List objects in the active scene") and scopes it with filtering, pagination, and hierarchy, which cleanly separates it from siblings like list_materials. It stops short of explicitly naming a sibling as an alternative, so it does not quite reach the top tier.

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: an agent can infer this is the tool for enumerating scene objects, and the mention of filtering/pagination hints at large-scene workflows. There is no explicit when-to-use guidance, no exclusions, and no pointer to an alternative for related enumerations.

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