Skip to main content
Glama
Sign In
PrusaSlicer-MCP

PrusaSlicer-MCP

by JorgeAlbareda
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

export_3mf

Save the current print bed, including objects, positions, and configuration, to a specified path as a 3MF project for sharing or later use.

Instructions

Export the bed (objects, positions and configuration) as a 3MF project.

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": {
      "output_path": "<output_path>"
    },
    "name": "export_3mf"
  }
}

Input Schema

NameRequiredDescriptionDefault
output_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that the export captures objects, positions and configuration, but says nothing about whether an existing file at output_path is overwritten, what permissions or directory requirements apply, or what the tool returns on success/failure.

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 efficient sentence that front-loads the verb and resource with the clarifying parenthetical immediately after. No wasted words, though it is arguably too terse given what it omits.

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 export tool with no annotations and no output schema, the description adequately conveys the operation's purpose and content scope, but leaves path semantics and overwrite behavior unaddressed, which are the main things an agent would need to invoke it correctly.

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 coverage is 0% for the single parameter, so the description must compensate and does not. It never explains output_path expectations such as format, required extension, or whether a directory must pre-exist.

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 ('Export') and resource ('the bed'), and clarifies the scope of what is exported (objects, positions and configuration) plus the output format (3MF project). This distinguishes it from siblings like upload_gcode or save_profile_as, though it never names those alternatives.

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 guidance on when to use this tool versus alternatives such as slice, upload_gcode, or save_profile_as. No prerequisites, no indication of when a 3MF export is preferable to other export/save paths.

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