Skip to main content
Glama

blender_selection

Read-onlyIdempotent

Select objects in Blender scenes by name, type, material, or use bulk actions like all, none, and invert. Adjust selection mode with replace, add, or subtract.

Instructions

Select objects and elements in Blender scenes.

Supports multiple operations through the operation parameter:

  • select_objects: Select specific objects by name

  • select_by_type: Select all objects of a specific type

  • select_by_material: Select objects using a specific material

  • select_all: Select all objects in scene

  • select_none: Deselect all objects

  • invert_selection: Invert current selection

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoSelection mode (REPLACE, ADD, SUBTRACT)REPLACE
operationNoSelection operation typeselect_objects
object_typeNoType of objects to select (MESH, CURVE, LIGHT, etc.)MESH
object_namesNoList of object names to select
active_objectNoObject to set as active after selection
material_nameNoMaterial name to select objects by

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the safety profile is covered. The description adds the list of supported operations, which is useful context, but it does not describe selection mode interactions or any other behavioral details beyond what the operation names imply.

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?

The description is concise, uses a clear bulleted list, and every sentence serves a purpose. It efficiently communicates the tool's capabilities without redundancy or fluff.

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?

The tool is low-complexity, the schema covers all parameters, and annotations cover safety. The description lists all supported operations, making it complete for understanding the tool's main behavior. Minor gap: no mention of selection mode (REPLACE/ADD/SUBTRACT) semantics, but that is a parameter detail covered by the schema.

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 each parameter is already documented. The description adds a semantic grouping of operations to parameters, but it doesn't provide additional meaning beyond the schema descriptions. Baseline 3 is appropriate when schema fully covers parameters.

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's purpose: 'Select objects and elements in Blender scenes.' It lists specific operations (select_objects, select_by_type, etc.) that make its scope and function unambiguous, distinguishing it from generic Blender tools.

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?

The description implies usage by listing the available operations, but it does not explicitly explain when to use this tool versus alternatives, nor does it provide exclusions or when-not-to-use guidance. The context is clear for simple selection tasks, but it lacks explicit guidance relative to sibling tools.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sandraschi/blender-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server