Skip to main content
Glama

get_material_nodes

Lists nodes in a Blender material node tree so you can inspect a material's shader components and structure before editing or debugging.

Instructions

List nodes in a material node tree.

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": {
      "name": "<name>"
    },
    "name": "get_material_nodes"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. "List" implies a read-only operation, but it says nothing about error behavior when the material has no node tree, whether the result is flat or hierarchical, or any permission requirements.

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

Conciseness3/5

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

The single sentence is front-loaded and free of filler, but its brevity comes at the cost of under-specification rather than genuine efficiency. Nothing is redundant, but too little is said.

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?

Although an output schema exists (so return values need not be described), a one-parameter lookup tool still needs the parameter's referent and basic failure behavior spelled out. Neither is present, so the definition is thin relative to even this modest complexity.

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% and the sole parameter is just "name" with no description, so the description must clarify whether it means material name, node tree name, or object name. It does not, leaving the single required parameter's meaning undefined beyond a generic label.

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 nodes in a material node tree" gives a specific verb (List) and resource (nodes in a material node tree), which is clearly distinct from the mutating counterpart set_material_nodes. It does not explicitly name or differentiate against any sibling, and it is ambiguous whether "material node tree" is scoped by the material name or a node-group name.

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?

The description offers no when-to-use guidance, no prerequisites, and no mention of the obvious alternative (set_material_nodes) or how to obtain the required name. Only the bare action is implied, so the agent must guess the appropriate context.

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