Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

inspect_compositor_pipeline

Inspect the active Blender compositor pipeline, nodes, links, and enabled render passes to verify setup or diagnose compositing output issues.

Instructions

Inspect the active Blender 5.2.2 LTS compositor pipeline, nodes, links, and enabled render passes.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "inspect_compositor_pipeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
scene_nameNoOptional scene name (defaults to active scene).

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 provided, the description carries the full burden, and 'Inspect' does signal a non-mutating read. It enumerates the facets covered (pipeline, nodes, links, check render passes), but says nothing about return shape, whether the scene must be open, or what happens with an invalid scene name.

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?

One front-loaded sentence that names the resource and the inspected facets with no filler or repetition. Every phrase earns its place.

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?

For a simple read-only inspection with one optional parameter and no output schema, the description covers scope and the inspected elements adequately. A brief note on whether changes are ever made or on prerequisites would close the remaining gap.

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 description coverage is 100% for the single optional scene_name parameter, so the schema already conveys its meaning and default. The description adds no parameter-level detail beyond that, which meets the baseline for fully documented schemas.

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') with a specific resource ('compositor pipeline, nodes, links, and enabled render passes'), so the agent knows exactly what will be read. It does not, however, distinguish this read-only inspection from the sibling tools configure_compositor and manage_compositor, leaving the boundary implicit.

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 or when-not-to-use guidance, and no alternative is named. The word 'active' hints at the default scope, but nothing tells the agent when to prefer this over configure_compositor or manage_compositor_nodes.

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