Skip to main content
Glama

get_blendfile_summary_missing_files_for_cli

Read-only

Detect missing external file references in a Blender .blend file by opening it in background Blender. Identify broken asset links before rendering or handoff.

Instructions

Find missing external file references used by the blend file. 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_missing_files_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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful runtime context by stating the blend file is opened in background Blender, implying a Blender process launch and a potentially slow operation. It stops short of noting whether Blender must be installed, whether the file is locked, or cost implications.

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 short sentences with the outcome front-loaded and no filler. The second sentence is a fragment ('Open blend_file in background Blender') whose subject is ambiguous, but the overall size is appropriate for a simple lookup tool.

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?

An output schema exists, so return values need not be explained, and the read-only profile is covered by annotations. Still missing is the CLI-vs-non-CLI distinction and any path or environment prerequisites, which matter for a tool that shells out to background Blender.

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?

Only one parameter and schema description coverage is 0%, so the description must carry the burden. Saying 'Open blend_file in background Blender' does imply the parameter is a path to a .blend file that will be loaded, but it does not clarify path format (absolute vs relative), whether the file must exist locally, or what happens on a missing file. The addition is marginal over the schema title 'Blend File'.

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 resource: 'Find missing external file references used by the blend file.' An agent knows exactly what the tool returns. However, it does not distinguish this '_for_cli' variant from the near-identical sibling 'get_blendfile_summary_missing_files', leaving the variant choice ambiguous.

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 and no mention of alternatives. The phrase 'Open blend_file in background Blender' hints at a headless CLI execution context, but the agent must infer when this variant is preferable to the non-CLI sibling or to path_info/datablocks summaries.

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