Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

inspect_material_shader

Read a Blender material's shader graph to capture exact node types, input values, and socket-identifier links without enabling nodes or altering materials.

Instructions

Read-only material graph snapshot: exact node types, supported input values and socket-identifier links. Never enables nodes or changes materials.

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

Input Schema

NameRequiredDescriptionDefault
target_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose a meaningful behavioral trait — that it will not enable nodes or mutate materials — which matters in node-graph contexts where inspection could trigger side effects. However, it says nothing about failure behavior for an invalid target, permissions, or output size, leaving real behavioral gaps.

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?

Two compact sentences, front-loaded with what the tool returns and followed by the read-only guarantee. No redundant or filler wording.

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?

There is no output schema, and the description usefully summarizes the returned structure (node types, input values, socket links), which is what an agent needs to trust the result. The remaining shortfall is the undefined target parameter and unstated error behavior, but for a one-parameter read tool the coverage is largely adequate.

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% for the single required parameter, target_name, and the description never explains what it identifies — a material, an object, or a node group. With the schema offering only a string type and length bounds, the definition does not compensate for the coverage gap.

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+resource ('Read-only material graph snapshot') and enumerates the returned content: node types, supported input values, and socket-identifier links. It implies the read-only counterpart to configure_material_shader through negation rather than naming a sibling, so differentiation is implicit rather than explicit.

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

Usage Guidelines3/5

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

The read-only framing implies when to use it (inspection before configuring) but never states a when-to-use condition or names an alternative such as configure_material_shader. No prerequisites or exclusions beyond 'never changes materials' are given.

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