Skip to main content
Glama
Sign In
blender-mcp-bridge

blender-mcp-bridge

by otinori
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

blender/list_objects

Retrieve a list of all objects in the Blender scene, including their names, types, and locations. Optionally filter by object type such as MESH, LIGHT, or CAMERA.

Instructions

シーン内オブジェクト一覧（名前・type・位置）を返す

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

Input Schema

NameRequiredDescriptionDefault
typeNoフィルタするオブジェクトタイプ（MESH / LIGHT / CAMERA 等）

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, and the description only states return values and filter parameter. It does not disclose read-only behavior, permission requirements, or performance characteristics.

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?

The description is a single concise sentence that communicates the core functionality without waste. However, it is only in Japanese, which may limit universality.

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?

For a list tool with no output schema and no annotations, the description is insufficient. It does not mention pagination, sorting, or the exact response structure beyond three fields.

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 100% and the parameter description is clear. The tool description adds minimal extra value by repeating the filter concept in Japanese, but does not explain format or defaults.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool returns a list of objects with name, type, and position. It uses a specific verb (list) and resource (objects), and is distinguishable from siblings like get_object or create_object.

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?

The description provides no guidance on when to use this tool over alternatives like blender/get_scene_info or how to filter effectively. With several sibling tools, explicit guidance is missing.

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