Skip to main content
Glama

get_blendfile_summary_of_linked_libraries

Read-only

Lists a Blender file's direct and indirect linked library dependencies so you can inspect external assets and resolve missing or nested references.

Instructions

List the file's direct and indirect Blender library dependencies.

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": "get_blendfile_summary_of_linked_libraries"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

A3.6/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 bar is lower. The description does add one genuinely useful behavioral fact — that dependencies are reported transitively, not just direct ones — but says nothing about depth limits, cycle handling, or what a 'dependency' encompasses. With an output schema present, the return shape need not be spelled out.

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?

A single front-loaded sentence with no filler, hedges, or redundant restatement of the tool name. Every word earns its place.

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?

For a zero-parameter, read-only tool with a rich output schema and clear annotations, the description is sufficient to call the tool correctly. The remaining gap is that an agent cannot tell from the text whether to use this or the '_for_cli' sibling, which the definition leaves entirely undifferentiated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter semantics to explain; baseline 4 applies. The description correctly avoids inventing or restating parameter information.

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?

States a specific verb ('List') and a specific resource ('Blender library dependencies'), plus a meaningful scope qualifier ('direct and indirect'). It does not distinguish itself from the near-identical 'get_blendfile_summary_of_linked_libraries_for_cli' sibling, which is the only thing keeping this from a 5.

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 by the narrow scope of the resource described; there is no explicit statement of when to reach for this versus the CLI variant or versus the datablock/missing-files summaries in the same family. No exclusions, preconditions, or alternatives are named.

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