Skip to main content
Glama

blender_get_node_tree

Read-onlyIdempotent

Retrieve the structure of shader, compositor, or geometry node trees to inspect connections and settings before making edits.

Instructions

Read the structure of any node tree — shader, compositor, or geometry nodes. Supports all 7 contexts.

Use this when: you need to understand node graph structure before editing.

Do NOT use for: editing nodes (use blender_edit_nodes).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tree_typeYesNode tree type.
contextYesContext: SHADER uses OBJECT|WORLD|LINESTYLE|NODE_GROUP, COMPOSITOR uses SCENE|NODE_GROUP, GEOMETRY uses MODIFIER|TOOL|NODE_GROUP.
targetNoTarget: material name (SHADER/OBJECT), world name (SHADER/WORLD), 'Object/Modifier' (GEOMETRY/MODIFIER), or node group name (NODE_GROUP).
depthNo'summary': name/type only. 'topology': connected sockets + non-default values (recommended). 'full': all data.topology
skip_defaultsNoIf True, omit inputs with default values (reduces tokens).
expand_groupsNoRecursively expand node groups.
max_depthNoMax recursion for group expansion.
Behavior4/5

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

Annotations already declare readOnly=true, idempotent=true. Description adds that it reads structure and supports all contexts, which complements annotations without contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely concise: two purpose sentences plus two usage guidelines. No wasted words. Front-loaded with core action.

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

Completeness4/5

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

No output schema, but description clarifies what is returned (node graph structure). Parameters are well-documented in schema, and annotations cover safety. Slightly lacking detail on output format, but adequate.

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 coverage is 100% with good parameter descriptions. Tool description does not repeat param details, which is acceptable. Baseline score of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states verb 'read', resource 'node tree structure', and scope covering shader, compositor, geometry nodes with all 7 contexts. Distinguishes from sibling blender_edit_nodes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit 'Use this when' and 'Do NOT use for' with alternative tool named (blender_edit_nodes). Provides clear context for selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ageless-h/blender-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server