Skip to main content
Glama

get_blendfile_summary_path_info

Read-only

Reports save status, path, size, age, and numbered backups for the current Blender file, helping verify file state and backup availability.

Instructions

Report save status, path, size, age and numbered backups for the blend file.

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_path_info"
  }
}

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.7/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 safety is covered; the description adds real value by enumerating what is reported, including two non-obvious data points (file age and numbered backups). It does not discuss behavior on unsaved/untitled files or what happens when no backups exist, which is the remaining gap.

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 the verb first and the reported fields enumerated; every word carries information and there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no parameters, an output schema, and annotations covering the safety profile, the definition needs only to identify what is reported, which it does. The one thing an agent still cannot resolve from the description is when to pick this versus the parallel _for_cli variant.

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 meaning to convey and the baseline of 4 applies. The description does not imply any hidden input options, which is consistent with the empty schema.

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?

"Report save status, path, size, age and numbered backups for the blend file" gives a specific verb plus an enumerated set of resources, which separates it from siblings like get_blendfile_summary_datablocks or get_blendfile_summary_missing_files. It stops short of differentiating itself from the parallel get_blendfile_summary_path_info_for_cli sibling, so the boundary is clear but not exhaustively drawn.

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 or when-not-to-use guidance and no named alternative; the agent must infer that this is the tool for questions like "is the file saved?" or "where is it on disk?". Nothing addresses the obvious ambiguity with the _for_cli counterpart.

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