Skip to main content
Glama

inspect_nodes

Inspect shader, geometry, or compositor nodes, sockets, and links with pagination to review and debug node setups in a Blender session.

Instructions

Inspect shader, geometry or compositor nodes, sockets and links with pagination.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
limitNo
offsetNo
owner_typeNomaterial
session_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It mentions pagination and implies a read-only inspection, but does not state permissions, side effects, return shape, or error behavior.

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 definition is a single front-loaded sentence with no wasted wording. 'With pagination' is useful but slightly redundant with the schema's limit and offset fields.

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?

For a five-parameter tool with two required parameters, no annotations, and no output schema, the description is too thin. It does not explain what 'name' identifies, how session_id is used, or what the inspection returns.

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 all five parameters. The description hints at pagination for limit/offset, but does not explain name, session_id, or owner_type, and does not map the node domains to the owner_type enum.

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 uses a specific verb ('Inspect') and names the resource precisely: shader, geometry, or compositor nodes, plus sockets and links. It is clear what the tool operates on, though it does not explicitly differentiate itself from siblings such as inspect_object or inspect_scene.

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 explicit when-to-use guidance, no prerequisites, and no alternatives named. The node domains imply the tool is for node graphs, but an agent gets no help deciding between this and inspect_object, inspect_scene, or inspect_dependencies.

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