Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

select

Toggle an object's selection state in the active Blender scene, optionally make it active and clear other selections before applying.

Instructions

Selects or deselects an object in the active scene and optionally makes it the active object. Supports clearing existing selections with deselect_all.

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

Input Schema

NameRequiredDescriptionDefault
nameYesExact target object name.
stateNoWhether to select (True) or deselect (False) the target object. Defaults to True.
task_idNoOptional task or workflow identifier.
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
make_activeNoOptionally make the target the active object when selecting. Defaults to True.
deselect_allNoOptionally deselect all other objects before applying selection. Defaults to False.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations exist, so the description bears the full burden. It does disclose meaningful behavior: selection can be toggled off via state, other objects can be cleared with deselect_all, and the target can become the active object — these are genuine side effects. It says nothing about behavior when the name is unknown, whether selection is additive by default, or what the scene state becomes, which is thin for a mutation 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?

Two tight sentences, no filler, with the primary action front-loaded and the secondary capabilities following. Nothing could be removed without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter mutation tool with no annotations and no output schema, the description covers the headline behaviors but omits error handling, the effect of task_id, and the meaning of the deprecated 'approved' flag. It is adequate to attempt a call but not to predict the outcome reliably.

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%, so every parameter (name, state, make_active, deselect_all, task_id, approved) is already documented in the schema. The description restates the make_active and deselect_all behaviors without adding format, ordering, or interaction semantics beyond what the schema provides, so the baseline of 3 applies.

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?

Names a concrete verb and resource ('Selects or deselects an object in the active scene') plus the secondary effect of making it active, so the operation is understandable. However, it offers no differentiation from the sibling tool 'select_object', which reads like it does the same thing, leaving the agent to guess which to call.

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 explains capabilities (deselect_all, make_active) but never states when this tool should be chosen over an alternative or what preconditions apply. With a near-identical sibling present, the absence of any routing guidance is a real gap.

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