Skip to main content
Glama

get_blendfile_summary_usage_guess

Read-only

Estimate Blender workflows from evidence in a .blend file to understand how a scene is used or intended to be used.

Instructions

Estimate Blender workflows from evidence in 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_usage_guess"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

B3.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), so the description's job is to add behavior. It does so meaningfully by framing the output as an estimate/guess derived from evidence, signalling to the agent that results are heuristic inference rather than authoritative facts. It stops short of saying what evidence is used or how confident the inference is.

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?

One short sentence with the verb and source of data front-loaded; nothing is redundant. It is efficient but so terse that the single clause carries an unusually heavy interpretive load.

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 no parameters, an output schema, and clear read-only annotations, the structural burden on the description is low, and it need not describe return values. Still, for a heuristic estimator the description leaves the key concept ('workflows') and the nature of the underlying evidence unexplained, which an agent would need in order to trust or route to this tool.

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 document; the baseline of 4 applies. The description correctly implies the input is the currently loaded blend file rather than an argument.

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?

The description states a verb ('Estimate') and a target ('Blender workflows') derived from 'evidence in the blend file', so the general function is graspable. However, 'workflows' is undefined — the agent cannot tell whether this means addons, operators, modifiers, or something else — and nothing distinguishes it from siblings such as get_blendfile_summary_datablocks.

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 when a different summary tool (or the _for_cli variant) would be preferable. The agent must infer applicability entirely from the name.

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