Skip to main content
Glama

get_selected_objects

Lists currently selected objects in Blender so AI clients can inspect the active selection before modeling, shading, animating, or adjusting scene operations.

Instructions

List currently selected objects.

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": "get_selected_objects"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full burden and delivers very little: "List" implies a read-only operation but does not state it, nor does it describe side effects, ordering, or the empty-selection case. The presence of an output schema covers return structure, but behavioral traits beyond that remain undisclosed.

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?

A single front-loaded sentence with no filler or repetition, which is the right shape for a trivial zero-argument call. It is arguably terse to the point of under-specification rather than verbose.

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 simple zero-parameter tool with an output schema, the core question an agent needs answered is which of the many object-getting siblings to call, and this definition addresses that only obliquely. It is adequate but leaves the selection-vs-scene-vs-active boundary implicit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter meaning to add; the baseline of 4 applies. Nothing in the description misleads about inputs.

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?

"List currently selected objects" gives a clear verb (list) plus a specific resource (the current selection), which distinguishes it in substance from get_objects. It never names or contrasts with siblings like get_objects or get_active_object, so an agent must infer the boundary rather than read it.

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 word "currently" implicitly signals that this reflects live selection state rather than the full scene, which hints at when to prefer it over scene-wide listing. There is no explicit when-to-use, no exclusion of alternatives, and no note about what happens when nothing is selected.

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