Skip to main content
Glama

get_node_tree

Retrieve the complete node tree of a Blender material, including all nodes, links, unlinked input values, and node settings for inspection or editing.

Instructions

Get the full node tree of a material (all nodes and links).

Args: material_name: Name of the material.

Returns: Dict with nodes (name, type, location, input and output names, the values of unlinked inputs, and the node's own settings) and links.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "material_name": "<material_name>"
    },
    "name": "get_node_tree"
  }
}

Input Schema

NameRequiredDescriptionDefault
material_nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.2

TDQS

B3.2/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does disclose that the return includes nodes, links, unlinked input values, and node settings. The verb 'Get' implies read-only behavior, though it does not mention material-not-found behavior or permission constraints.

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 description is front-loaded with the purpose and then cleanly separates Args and Returns. It is reasonably concise, though the detailed return summary may partly duplicate the output schema.

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 one-parameter getter with an output schema, the description covers purpose, parameter, and return shape. However, it lacks guidance on sibling selection and does not clarify material lookup failure behavior.

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?

The single parameter is only described as 'Name of the material,' which mostly restates the property name. Schema description coverage is 0%, and the description does not add expected naming format, case sensitivity, or existence requirements.

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: retrieving the full node tree of a material, including all nodes and links. This is clear enough to distinguish it from most shader-node mutation tools, though it does not explicitly differentiate itself from the similar sibling get_geometry_node_tree.

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?

It does not explain when to use this tool versus alternatives such as get_geometry_node_tree or list_materials. There are no exclusions, prerequisites, or explicit routing guidance; use is only implied by the tool purpose.

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