Skip to main content
Glama

get_blendfile_summary_datablocks_for_cli

Read-only

Summarizes datablock counts, scene, workspace, and render engine by opening a .blend file in background Blender, so you can inspect file contents without launching the UI.

Instructions

Summarize datablock counts, scene, workspace and render engine. Open blend_file in background Blender.

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

Input Schema

NameRequiredDescriptionDefault
blend_fileYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuine context beyond them: the file is loaded into a background Blender instance, which tells the agent this spawns a heavyweight external process requiring a real path. It does not mention cost, latency, or failure behavior for a missing/invalid file, keeping it short of a 5.

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?

Two tight sentences with zero filler, and the primary purpose is front-loaded before the execution detail. The first sentence is a compressed feature list rather than flowing prose, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Return values are covered by the existing output schema and safety by the annotations, so the description's remaining burden is light. However, for a tool that launches Blender in the background it says nothing about prerequisites (Blender availability/version), expected runtime, or how it differs from the non-CLI variants, leaving an agent to guess at operational constraints.

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 0% for the single parameter, so the schema alone says only 'blend_file: string'. The description partially compensates by implying it is a path to a .blend file that Blender opens in the background, but it gives no format, path style, or handling for relative paths and nonexistent files.

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 names a specific verb and concrete outputs: 'Summarize datablock counts, scene, workspace and render engine.' An agent immediately knows what data comes back. It stops short of differentiating this from the near-identically named sibling get_blendfile_summary_datablocks (the '_for_cli' distinction is never explained), so sibling disambiguation is left to inference.

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: 'Open blend_file in background Blender' signals this works on a file on disk by spawning a background process rather than on the current session. There is no explicit when-to-use, when-not-to-use, or named alternative despite several sibling summarizers existing, so the agent must infer which summary variant to call.

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