Skip to main content
Glama

get_blendfile_summary_of_linked_libraries_for_cli

Read-only

Lists a Blender file's direct and indirect linked library dependencies by opening it in background Blender, enabling dependency audits before sharing or archiving.

Instructions

List the file's direct and indirect Blender library dependencies. 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_of_linked_libraries_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 and the description's claim of listing dependencies is consistent with it. The added value is the disclosure that the tool opens the file in a background Blender process, which signals startup latency and that the path must be reachable by the server. It says nothing about behavior when libraries are missing or unreadable.

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 primary purpose front-loaded and no filler. The second sentence is a terse, slightly telegraphic fragment ('Open blend_file in background Blender'), but it still earns its place by adding operational context.

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 described, and the annotations carry the safety profile. What is missing for a tool that spawns a Blender process is any note on prerequisites (valid absolute path), cost/timeout expectations, or how it differs from the non-CLI variant.

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%, so the single parameter must be explained in prose, and the description only implies that blend_file is a file Blender opens. It does not state that it is an absolute filesystem path, whether it is server-side, or what formats/extensions are accepted — a real gap for a required path parameter.

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 — 'List the file's direct and indirect Blender library dependencies' — and even scopes it to direct and indirect dependencies, so an agent knows exactly what comes back. It does not, however, distinguish this from the sibling get_blendfile_summary_of_linked_libraries, leaving the agent to infer the CLI/background distinction from the name alone.

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?

'Open blend_file in background Blender' implies this tool spawns its own headless Blender instance rather than using an existing session, which hints at when it applies. But there is no explicit when-to-use statement, no exclusion, and no pointer to the non-CLI sibling for comparison.

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