Skip to main content
Glama

ai_modeling_local_convert

Convert self-contained GLB files locally with Blender to FBX, OBJ, STL, USDZ, or 3MF without Studio requests or credits.

Instructions

convert a self-contained GLB locally with Blender; no Studio request or credits

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": {
      "model_path": "<model_path>",
      "destination_path": "<destination_path>",
      "format": "<format>"
    },
    "name": "ai_modeling_local_convert"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatYes
blenderNo
model_pathYes
part_namesNoKeep only these exact mesh/node names from the exported GLB, using local processing.
scale_factorNo
flatten_bottomNo
texture_formatNoLocal texture encoding: OBJ/FBX support all listed formats; GLB PNG/JPEG/WEBP; USDZ PNG.
source_metadataNoApply Studio metadata to the original GLB before conversion; do not use an already edited export.
destination_pathYes
pivot_to_center_bottomNo
flatten_bottom_thresholdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the description's job is additive context. It adds useful facts (Blender runs locally, no Studio call, no credits), but says nothing about destination file overwrite behavior, runtime cost, whether Blender must be preinstalled, or what 'self-contained' actually excludes.

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?

A single tight sentence with zero filler and the key differentiator (local, no credits) front-loaded. It is efficient, though the brevity contributes to gaps elsewhere rather than being a flaw of structure itself.

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 11-parameter, 3-required mutation tool that writes an output file, with no output schema and no annotations about side effects. The description covers neither the parameter surface (part filtering, texture format constraints, metadata application ordering) nor the result, which is too thin for this complexity.

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 only 27% across 11 parameters, including a nested source_metadata object and edge-case params like flatten_bottom_threshold, pivot_to_center_bottom, scale_factor and blender. The description mentions none of them and so does not compensate for the coverage gap, leaving most parameters to bare names and types.

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: 'convert a self-contained GLB locally with Blender'. The word 'convert' plus the 'self-contained GLB' scope distinguishes it reasonably from ai_modeling_local_edit, but no sibling is named explicitly.

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

Usage Guidelines4/5

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

'no Studio request or credits' gives a clear selecting condition: pick this when you want offline conversion without consuming credits. It also implies the input must be self-contained. It stops short of naming exclusions (e.g., when to prefer the Studio-side or edit path instead).

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