Skip to main content
Glama

get_objects

List Blender scene objects with optional name and type filters plus pagination, so AI clients can inspect and select the 3D assets they need.

Instructions

List objects with optional filtering and pagination.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
name_filterNo
object_typeNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description must carry the full behavioral burden. It implies a read operation but does not state that it is non-destructive, whether results include all scene objects or only visible/selected ones, what ordering is applied, or how pagination totals are exposed. For a listing tool with zero annotation coverage, this is a significant gap.

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?

The single sentence is front-loaded and free of filler, making it easy to scan. It is arguably too terse, but that is better assessed under contextual completeness rather than verbosity.

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

Completeness2/5

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

For a four-parameter list tool with 0% schema description coverage and no annotations, the definition is under-specified about filtering semantics, pagination behavior, and what objects are in scope. The existing output schema helps with return values, but the input and behavioral context remain thin.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must explain all four parameters. It only generically groups them as 'filtering' and 'pagination' without clarifying limit/offset defaults, whether name_filter is a substring or exact match, or what object_type values are accepted.

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 ('List objects') plus its two capabilities (filtering and pagination), so the agent knows this is a read/list operation. However, it never distinguishes this from siblings such as get_selected_objects, get_scene_hierarchy, or get_object_info, leaving ambiguity about scope.

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?

There is no guidance on when to use this tool versus the many object-related siblings, nor any prerequisites or exclusions. 'Optional filtering and pagination' describes capability, not when-to-use criteria.

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