Skip to main content
Glama

get_blendfile_summary_path_info_for_cli

Read-only

Reports a Blender file's save status, path, size, age, and numbered backups by opening it in background Blender for CLI inspection.

Instructions

Report save status, path, size, age and numbered backups for 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_path_info_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
Behavior4/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 a genuinely non-obvious behavioral fact beyond that: the tool spawns/opens the file in a background Blender instance, which implies latency and a Blender dependency that the agent would otherwise not know. It omits failure behavior when the path is invalid or Blender is unavailable, 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 short sentences with no filler, and the most useful content (the reported fields) is front-loaded. The second sentence is a fragment and slightly telegraphic, but it conveys a distinct fact rather than padding.

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 no explanation, and the tool is simple with one required parameter. What is missing is the CLI-versus-other-variant distinction and any hint about path format or file existence requirements. Adequate for a low-complexity tool but not complete.

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 coverage is 0% and the single parameter blend_file has no description in the schema. The description only restates the parameter name, giving no guidance on whether an absolute path, relative path, or existing .blend file is required. An agent can guess, but the definition does not compensate for the coverage gap.

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 set: report save status, path, size, age and numbered backups for the blend file, and states it opens the file in background Blender. That is far more informative than the name alone. It does not differentiate itself from the closely named sibling get_blendfile_summary_path_info, so an agent must guess which variant to pick.

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 stated preconditions, and no mention of alternatives such as the non-CLI path_info sibling or the other summary tools. The only usage signal is implicit in the name suffix '_for_cli' and the phrase 'in background Blender', which is not an explicit routing instruction.

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