Skip to main content
Glama
solidworks-mcp

solidworks-mcp

sw_open_in_bambu

Opens an STL file in the Bambu Studio GUI so you can manually slice and print it when command-line slicing is unavailable.

Instructions

把 STL 交给 Bambu Studio 界面打开,供人工切片与打印。

部分 Bambu Studio 版本(如 02.09.01.70)无命令行切片能力,因此采用 「自动打开 GUI + 人工点切片/打印」的半自动方案。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sw_open_in_bambu"
  }
}

Input Schema

NameRequiredDescriptionDefault
stl_pathNo

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 provided, so the description carries the full burden. It does disclose the most important traits — launching an interactive GUI and leaving slicing/printing to a human — but is silent on blocking behavior, whether it waits for the GUI, failure modes, or whether anything is returned.

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?

The purpose is stated in the opening sentence and the design rationale follows, with no filler. The line breaks are somewhat awkward but the content is tight and front-loaded.

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

Completeness3/5

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

For a one-parameter GUI-launch tool with no annotations and no output schema, the description covers what it does and why the human-in-the-loop step exists. It leaves gaps around the only parameter's semantics and what happens after the GUI is launched.

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% for the single stl_path parameter, so the description must compensate and largely does not. It only implies the parameter is an STL file path; it never explains the expected format, whether the file must already exist, or what an empty default value does.

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?

The description states a concrete verb and resource: it hands an STL file to the Bambu Studio GUI to be opened. It is clearly distinct from export-style siblings, but it never explicitly contrasts itself with alternatives such as sw_export_stl or sw_check_printability, so an agent must infer the boundary.

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 provides the rationale for use — some Bambu Studio versions lack CLI slicing, so this semi-automatic flow exists — which is genuine context. However, it gives no explicit when-not condition, no prerequisite checks (e.g. Bambu Studio installed, STL already exported), and no named alternative to route to.

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