Skip to main content
Glama

get_collections

List collections in the current Blender scene to inspect organization and choose which collection to work with.

Instructions

List collections in the scene.

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

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.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses almost nothing: no statement that the call is a read-only operation, no indication of whether nested/child collections are included, and no mention of ordering or result size. The one behavioral fact an agent can extract is that results are scoped to the current scene.

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, dead wording, or hedging. It is efficiently structured, though its brevity leans toward under-specification rather than crisp minimalism.

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?

Complexity is minimal (no parameters, output schema present so return values need no explanation), which lowers the bar considerably. Still, given six nearby collection/scene tools, the definition never states how the listing relates to per-collection detail tools or whether the hierarchy is flattened, leaving a small but real gap.

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 semantics to explain and 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 collections in the scene" gives a specific verb (list) and resource (collections) with explicit scope (in the scene), which is enough to tell it apart from get_objects or get_scene_info by resource alone. It does not, however, distinguish itself from the very close sibling get_collection_info, so an agent must infer that this is the enumeration counterpart rather than the detail lookup.

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 when-to-use or when-not-to-use guidance and no named alternative; the agent must infer that get_collection_info should be used once a specific collection is identified. The scope phrase "in the scene" is the only contextual constraint offered.

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