Skip to main content
Glama

export_scene

Export the entire 3D scene to a specified file path, with optional overwrite, enabling AI clients to save and share Blender work.

Instructions

Export the full scene.

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": {
      "path": "<path>"
    },
    "name": "export_scene"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
overwriteNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.2/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden and discloses almost nothing: it doesn't state that this writes a file, what format is chosen (or whether it is inferred from the path extension), whether missing directories are created, or what permissions/errors to expect. The presence of an 'overwrite' parameter implies file mutation, but the description never confirms or elaborates on it.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single front-loaded sentence with zero filler, which is structurally clean. But the brevity is under-specification rather than efficiency, so it cannot earn a high score for conciseness.

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

Completeness2/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 needn't be explained, but for a file-writing export operation with no annotations and 0% parameter documentation, the definition leaves critical gaps: format, destination semantics, and overwrite behavior. It is not complete enough for an agent to invoke confidently without inspecting the schema or trial and error.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for two parameters, and the description adds no meaning: 'path' could be a file path, directory, or base name with an inferred extension, and 'overwrite' semantics are unstated. The single sentence conveys nothing about either parameter.

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 gives a verb plus resource ("Export the full scene"), and the word "full" faintly distinguishes it from export_selected_objects and export_asset. However, it never says what export format, destination type, or fidelity is produced, so an agent still has to guess what 'export' concretely yields.

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 guidance, no mention of prerequisites, and no naming of alternatives such as export_asset or export_selected_objects. The scope word "full" is the only implicit routing signal, which is insufficient given several sibling export tools exist.

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