Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

inspect_render_output

Verifies a registered still-render receipt against the current output file using identity, SHA-256, and PNG integrity checks; unknown, expired, changed, or missing artifacts fail explicitly.

Instructions

Verify a registered still-render receipt against the current output file. Checks identity, SHA-256 and PNG CRC/dimensions/decoded scanlines. No caller file paths; unknown, expired, changed or missing artifacts fail explicitly.

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

Input Schema

NameRequiredDescriptionDefault
render_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/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 burden and does a fair job: it discloses the read-only verification nature, the exact checks (identity, SHA-256, PNG CRC, dimensions, decoded scanlines), the input restriction (no caller file paths), and explicit failure for unknown/expired/changed/missing artifacts. It does not state whether failure raises an error or returns a status value, which matters without an output schema.

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?

Three tight sentences: the verification action is front-loaded, the check list is compact, and the constraint and failure behavior follow in order of importance. No filler.

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 single-parameter verification tool with no annotations and no output schema, the description covers scope, checks, and failure modes well. The remaining gap is the success return shape and how a render_id comes into existence.

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 coverage is 0%, so the description must compensate. "Registered still-render receipt" and "no caller file paths" usefully clarify that render_id is an opaque registry token rather than a filesystem path, but it never says how that token is obtained or what it corresponds to structurally.

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?

"Verify a registered still-render receipt against the current output file" gives a specific verb and resource, and the still-render framing separates it from the many scene-data inspect_* siblings. It stops short of naming a competing alternative, but the action is unambiguous.

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?

Usage is only implied: the agent must infer that this runs after a render has been registered to obtain a render_id. There is no explicit when-to-use statement, no timing guidance (e.g., after render_scene completes), and no stated alternatives.

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