Select objects in Blender by name, replacing the current selection when needed. Use this to target specific objects for editing, animation, or scene management.
Select one or more objects by name.
Args: names: List of object names to select. replace: If True, deselect all others first.
| Name | Required | Description | Default |
|---|---|---|---|
| names | Yes | ||
| replace | No |
Changes observed during successful MCP inspections.
v3.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses the replace parameter behavior ('deselect all others first'), which implies additive selection when replace is False, but it does not cover invalid names, return values, or error handling. This is adequate for a simple selection tool but not comprehensive.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise and front-loaded with the core action, followed by clear parameter semantics. No extraneous words or redundancy; the structure is efficient and easy to scan.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a two-parameter tool with no output schema and no annotations, the description covers the essential selection behavior, but it omits return value, error behavior, and when to prefer this over sibling tools like batch_select. It is adequate but has clear informational gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With 0% schema description coverage, the description must compensate, and it does. It explains that names is a list of object names and that replace controls deselection of existing selection, adding real meaning beyond the schema's bare property titles.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool selects one or more objects by name, with a specific verb and resource. It does not explicitly differentiate from sibling tool batch_select, but the 'by name' qualifier makes the purpose sufficiently distinct.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is implied: use this tool when you need to select objects by name. The description provides no explicit when-to-use guidance or comparison to alternatives like batch_select, so it only meets the baseline implied-usage level.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.