Skip to main content
Glama
Ref2Blender MCP Server

Ref2Blender MCP Server

by evarynstudio

export_all_assets

Exports each asset sub-collection to its own file in a target folder, pivoting each on its base and applying LOD, collision, palette, and engine export options.

Instructions

Export every asset sub-collection to its own file in folder, each pivoted on its own base. Same options and same caution as export_model.

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": {
      "folder": "<folder>"
    },
    "name": "export_all_assets"
  }
}

Input Schema

NameRequiredDescriptionDefault
lodsNo
pivotNobottom
engineNounity
folderYes
paletteNo
collisionNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does usefully reveal that multiple files are written into `folder` and that each is pivoted on its own base, but the referenced 'caution' (likely overwrite or file-clobbering behavior) is never spelled out, and nothing is said about permissions, existing-file handling, or failure modes.

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?

Two short sentences with the destination and output shape front-loaded and no filler. Nothing is repeated from the schema and nothing is wasted.

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 described, but the description leaves five of six parameters undefined and defers behavioral caveats to a sibling. For a file-writing, unannotated, multi-file export tool, that is not enough for confident invocation.

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

Parameters2/5

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

Schema description coverage is 0% across six parameters, and the description explains only `folder`. The options lods, pivot, engine, palette, and collision are dismissed with 'same options as export_model,' which forces the agent to open another tool's definition to understand this one's arguments.

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?

States a specific verb and resource: exporting every asset sub-collection to its own file under `folder`, each pivoted on its own base. That scope ('every asset sub-collection' into separate files) is enough to tell it apart from export_model, though the description never explicitly names the contrast.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the scope word 'every' versus the single-model sibling; there is no explicit 'use this when X, use export_model when Y' and no statement of prerequisites. The phrase 'same caution as export_model' gestures at guidance but is a cross-reference rather than self-contained instruction.

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