Skip to main content
Glama
Sign In
PrusaSlicer-MCP

PrusaSlicer-MCP

by JorgeAlbareda
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_printer_status

Retrieve the current state, print progress, active file, and temperatures from a networked Prusa printer to monitor jobs and check readiness.

Instructions

State, progress, current file and temperatures of a networked printer.

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": {
      "host": "<host>"
    },
    "name": "get_printer_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYes

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 burden. It hints at the returned data (state, progress, current file, temperatures) but never states that this is a read-only operation, whether it contacts the printer live, what happens if the host is offline, or whether any auth is required. Significant behavioral gaps for the sole tool that probes a printer.

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?

One compact sentence that front-loads the returned content. No filler, though it is arguably under-specified rather than deliberately minimal.

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?

Reasonable for a simple one-parameter read tool with no output schema, and it enumerates most return fields. However, it leaves the 'host' identifier format and the failure/connectivity behavior unspecified, which an agent needs in order 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?

The single parameter 'host' has 0% schema description coverage and the description does nothing to clarify it beyond the phrase 'networked printer'. It does not say whether 'host' is an IP address, hostname, or a printer ID from list_print_hosts, which is exactly the ambiguity an agent needs resolved.

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 gives a specific verb ('State' – i.e., report) and resource (networked printer status) plus the fields returned (progress, current file, temperatures). It is clearly distinct from mutation siblings like start_print or cancel_print, though it does not explicitly name list_printers/list_print_hosts as 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 statement of when to use this vs. list_printers (which likely enumerates hosts) or list_print_hosts. Usage is only implied by the word 'status'. No prerequisites, no exclusions, no alternatives named.

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