Skip to main content
Glama

get_scene_summary

Retrieve a compact summary of the current Blender scene to quickly inspect its contents and layout.

Instructions

Return a compact summary of the current scene.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden, yet it discloses nothing beyond the fact that it returns something. It does not state that the call is read-only, that it targets the active scene implicitly, what scale of data "compact" implies, or whether it is cheap enough to call frequently. For a zero-parameter query tool these are the few facts that would actually help.

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, front-loaded sentence with no filler. It is efficient, though the brevity comes at the cost of the missing differentiation and behavioral detail rather than being a model of tight writing.

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 the return shape need not be described, and with zero parameters the input side is trivially complete. What remains missing is the relationship to sibling scene-query tools and any hint of the summary's scope, which for a tool embedded in a large scene-inspection family is a real gap.

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 no parameters and the schema is empty, so there is nothing for the description to disambiguate. The phrase "current scene" usefully signals that no scene identifier is accepted, which is the only parameter-adjacent meaning needed.

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?

"Return a compact summary of the current scene" gives a concrete verb and resource, so the basic action is understandable. However, the sibling set contains get_scene_info, get_scene_hierarchy and get_scene_settings, and the description never says how a "summary" differs from those. "Compact" is undefined, leaving the agent unable to tell which scene-reading tool 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 exclusions, and no mention of the closely related get_scene_info alternative. The agent must infer usage purely from the name, which is exactly the situation the description should prevent.

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

Deploy Server

Other Tools