Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

select_object

Select or deselect a named object in the active Blender scene, optionally make it active, and clear other selections before applying the change.

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_object"
  }
}

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.4/5.0
Behavior3/5

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

With no annotations at all, the description carries the full behavioral burden. It discloses the scope (active scene) and the default side effects (making the object active, clearing other selections), but says nothing about what happens when the name doesn't match an object, whether the change is undoable, or what state is returned.

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?

Two sentences, front-loaded with the core action and the optional side effect, with no filler. Slight redundancy in re-explaining deselect_all, which the schema already covers, keeps it from a 5.

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 state-mutating tool with no annotations and no output schema, the description covers the main action but omits failure modes and return behavior. It is adequate to call the tool, but not complete enough to predict what happens on a missing object name or how selection state feedback is delivered.

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 including the deprecated and untrusted approved flag is already documented. The description restates make_active and deselect_all in prose but adds no new meaning beyond the schema, so the baseline 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?

The description states a specific verb and resource — selecting/deselecting an object in the active scene — plus the active-object side effect. It is clear on its own, though it does nothing to separate itself from the sibling tool named "select", which an agent could easily confuse it with.

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 implied by "in the active scene" and by the mention of clearing selections, but there is no explicit when-to-use or when-not-to-use guidance and no naming of an alternative tool. Given a sibling literally called "select", the absence of routing guidance is a meaningful 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