Skip to main content
Glama
Sign In
PrusaSlicer-MCP

PrusaSlicer-MCP

by JorgeAlbareda
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

import_profile_bundle

Import a PrusaSlicer config bundle (.ini with [print:…] sections) as user profiles, with an option to overwrite existing profiles.

Instructions

Import a PrusaSlicer config bundle (.ini with [print:…] sections) as user profiles.

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": {
      "path": "<path>"
    },
    "name": "import_profile_bundle"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
overwriteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It hints at the effect ('as user profiles'), but says nothing about whether existing profiles are replaced, what overwrite defaults to, whether the operation is reversible, or what happens on a parse 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 tight sentence with the verb and resource front-loaded and no filler. It is efficient, though the brevity is partly under-specification rather than pure conciseness.

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?

For a file-importing mutation tool with no annotations, no output schema, and 100% of parameters undocumented in the schema, the description leaves too much unexplained — notably overwrite behavior and failure modes on a malformed bundle.

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%, so the description must compensate. It partially helps by describing the file content expected at 'path' (.ini with [print:…] sections), but says nothing about the 'overwrite' flag, which is the parameter with the most consequential semantics.

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 (Import) and resource (PrusaSlicer config bundle), and even names the expected file format with '[print:…]' sections, which distinguishes it from siblings like save_profile_as or use_config_file. It stops short of explicitly contrasting itself with those siblings, so it earns a 4 rather than a 5.

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 statement of when to use this tool versus alternatives such as use_config_file, select_profiles, or save_profile_as, all of which live in the same profile-space. No prerequisites or preconditions are given either.

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