Skip to main content
Glama

export_selected_objects

Export currently selected Blender objects to a specified file path, with an option to overwrite existing files.

Instructions

Export currently selected objects.

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

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?

No annotations are supplied, so the description carries the full behavioral burden and falls well short: it does not say that files are written to disk, what format is produced, what happens if the file already exists, or whether the export is reversible. 'Export' at least implies a write operation, but nothing else is disclosed.

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 padding, so structurally clean. But its brevity here reflects under-specification rather than economy: the one sentence says nothing an agent could not infer from the tool name.

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 need not be explained, but a file-writing tool with no annotations, an undocumented path parameter, an undocumented overwrite flag, and no format or destination information is materially incomplete. An agent could invoke it but could easily write to the wrong place or clobber files.

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 whatsoever. The critical ambiguity — whether 'path' is a directory or a full file path — plus what 'overwrite' actually does are both left entirely undocumented.

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?

"Export currently selected objects" gives a verb plus a bounded scope (the current selection), which distinguishes it in spirit from export_scene/export_asset. However, 'export' is left unqualified — no target, format, or destination — so the agent cannot tell what actually happens beyond a vague notion of writing something out.

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 at all: nothing says to prefer this over export_scene or export_asset, nor what preconditions (a non-empty selection) must hold. The selection scoping is the only implicit hint, and it is never stated as a rule.

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