Skip to main content
Glama
DMontgomery40

bambu-printer-mcp

by DMontgomery40
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

blender_mcp_edit_model

Import, edit, and export local STL files via Blender to decimate, remesh, or union meshes—producing verified output while preserving existing scene objects.

Instructions

Import, edit, and export a local STL through standard Blender MCP with verified output and existing scene objects preserved. Requires a shared local filesystem and Blender Object Mode. Also supports a separately configured legacy executable bridge.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
executeNoApply edits and export (true) or validate and return the prepared request without connecting (false, default).
stl_pathYesPath to the local STL file
operationsYesOrdered operations: decimate:<ratio greater than 0 and at most 1>, remesh:<positive voxel size in STL units>, boolean_union:<STL path>. Legacy custom bridges define their own operations.
timeout_msNoTotal Blender request deadline in milliseconds; defaults to BLENDER_MCP_TIMEOUT_MS or 120000.
output_pathNoRequired for standard MCP previews and execution: new local STL output path whose parent exists. Existing files are never overwritten. Optional for legacy-only bridge configuration.
user_promptNoThe user's own words describing the edit, passed unchanged to Blender MCP.
bridge_commandNoLegacy custom bridge executable override, not a standard MCP command. Per-call overrides require MCP_ALLOW_EXECUTABLE_ARG=1.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv1.1.14
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / bridge_command / description
      Previous value: -"Override command for invoking Blender MCP bridge"New value: +"Legacy custom bridge executable override, not a standard MCP command. Per-call overrides require MCP_ALLOW_EXECUTABLE_ARG=1."
    • changedInput schema / properties / execute / description
      Previous value: -"Execute bridge command (true) or return payload only (false)"New value: +"Apply edits and export (true) or validate and return the prepared request without connecting (false, default)."
    • changedInput schema / properties / operations / description
      Previous value: -"Ordered edit operations for Blender (e.g. remesh, boolean, decimate)"New value: +"Ordered operations: decimate:<ratio greater than 0 and at most 1>, remesh:<positive voxel size in STL units>, boolean_union:<STL path>. Legacy custom bridges define their own operations."
    • addedInput schema / properties / operations / maxItems
      Added value: +64
    • addedInput schema / properties / operations / minItems
      Added value: +1
    • addedInput schema / properties / output_path
      Added value: +{
+  "description": "Required for standard MCP previews and execution: new local STL output path whose parent exists. Existing files are never overwritten. Optional for legacy-only bridge configuration.",
+  "type": "string"
+}
    • addedInput schema / properties / timeout_ms
      Added value: +{
+  "description": "Total Blender request deadline in milliseconds; defaults to BLENDER_MCP_TIMEOUT_MS or 120000.",
+  "maximum": 300000,
+  "minimum": 100,
+  "type": "integer"
+}
    • addedInput schema / properties / user_prompt
      Added value: +{
+  "description": "The user's own words describing the edit, passed unchanged to Blender MCP.",
+  "type": "string"
+}
  2. First observedv1.1.1

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose notable traits: output is verified, existing scene objects are preserved, and it needs a shared filesystem and Object Mode. It omits the dry-run default (execute=false validates only), though that is covered in the schema.

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?

Two dense sentences that front-load the core pipeline and guarantees before the legacy-bridge caveat. The legacy sentence is niche but relevant; little is wasted.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter mutation tool with no output schema, the description supplies the key operational constraints (filesystem, Object Mode, non-destructive scene handling) and implies an export flow. It could state the validate-vs-apply default behavior more prominently, but coverage is adequate.

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

Parameters3/5

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

Schema description coverage is 100%, so every parameter (including the execute flag, operations format, timeout, and overwrite protection) is already documented. The description adds no parameter-level detail beyond that, making the baseline 3 appropriate.

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 chain and resource: import/edit/export a local STL through Blender MCP, which distinguishes it from siblings like blender_mcp_call, blender_mcp_status, and get_stl_info. It does not explicitly name a sibling alternative, but the scope is unambiguous.

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?

It gives prerequisites (shared local filesystem, Blender Object Mode) and notes a legacy bridge mode, which is real context. However, it never says when to use this tool versus blender_mcp_call or the other STL-manipulation siblings, so routing is left to inference.

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