Skip to main content
Glama

get_blendfile_summary_usage_guess_for_cli

Read-only

Opens a .blend file in background Blender and analyzes its evidence to estimate likely Blender workflows, helping infer how a blend file was used.

Instructions

Estimate Blender workflows from evidence in 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_usage_guess_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

C2.9/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 carried by structured data. The description does add a genuine behavioral trait beyond them — the file is opened in a background Blender instance, implying process spawn and non-trivial latency — but says nothing about failure modes (e.g., Blender not installed), cost, or whether the guess is speculative versus deterministic.

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 no padding, and the purpose is front-loaded ahead of the operational note. Slightly under-specified rather than verbose, so it earns nearly full marks for structure.

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?

With an output schema present, return values need not be explained, and the tool is simple with one required parameter. Still, the definition leaves the CLI-versus-non-CLI distinction and the background-process side effects unaddressed, which matters for an agent choosing among many blendfile-summary tools.

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 for the single blend_file parameter. "Open blend_file in background Blender" does clarify that it is a path to a .blend file that will be launched, which is useful, but it gives no format, path-resolution, or version-compatibility detail.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a verb ("Estimate") and resource ("Blender workflows") scoped to "evidence in the blend file," which is more than a tautology. However, "workflows" and "evidence" stay abstract, and the description never distinguishes this tool from its near-identical sibling get_blendfile_summary_usage_guess, so an agent cannot tell from the text why the _for_cli variant exists.

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 when-to-use guidance, no prerequisites, and no mention of the sibling get_blendfile_summary_usage_guess as the alternative. The agent must infer usage from the name alone.

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