SimplyPrint: 3D Print Farm Management

list_printers

Read-onlyIdempotent

List MULTIPLE printers with optional filters. For details on a single known printer, call get_printer instead — do not list-then-filter. For farm-wide counts ("how many printers are doing X"), call get_farm_overview instead — do not paginate this. Use status=["online"] to only see reachable printers, status=["printing"] for ones actively printing, status=["was_printing_when_offline"] for printers that dropped mid-print, status=["idle"] for available printers ready to accept a job, status=["awaiting_bed_clear"] for printers whose last print finished but the bed has not been cleared yet (NOT print_pending, which means a queued staggered start).

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	Page number (1-based) when paginating beyond limit/page_size.
`tags`	No	Filter printers that have any of the given tag names
`limit`	No	Cap on results (1-100). Alias for page_size. Use this with sort_by for "top N" queries.
`search`	No
`status`	No	Filter by status. Multiple values are OR-matched. Macros (derived): online, offline, idle, was_printing_when_offline, in_maintenance, print_pending, can_accept_commands, awaiting_bed_clear. Raw PrinterStatus: printing, operational, paused, pausing, resuming, cancelling, error, downloading, unknown. Note: awaiting_bed_clear means a print finished but the bed has not been cleared yet (online + operational + still has a job) — use this NOT print_pending (which means a queued/staggered start) when the user asks "which printers need to be cleared off?".
`compact`	No	Keep at default true. Returns minimal data tuned for AI context. Only set to false if you specifically need fields the compact view drops, and then pair with limit to keep the response small.
`sort_by`	No	Sort by this field. Default: stable (no sort).
`sort_id`	No
`group_id`	No	Only return printers in this printer group
`order_by`	No
`sort_dir`	No	Sort direction; default asc when sort_by is set.
`page_size`	No
`job_columns`	No
`out_of_order`	No	If true, only out-of-order printers; if false, only in-order printers (enterprise feature)
`printer_columns`	No
`filament_columns`	No

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already mark this as readOnly/idempotent/non-destructive, so the bar is lower, but the description adds valuable behavioral context: it returns multiple printers, supports filtering, and clarifies the nuanced meaning of the 'awaiting_bed_clear' status, including how it differs from 'print_pending'. This goes well beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, dense sentence that front-loads the main purpose, then efficiently covers alternatives and status meanings without redundancy. Every clause contributes to selection or invocation, making it concise despite its length.

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?

Given the 16 parameters and no output schema, the description focuses on the most ambiguous aspects (status filters and misuse scenarios) and adequately covers common usage. It doesn't elaborate on return format or pagination mechanics, but those are reasonably implied/covered by the schema and the 'do not paginate' warning.

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

Parameters5/5

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

While the schema covers 56% of parameters with descriptions, the description adds significant semantics for the 'status' parameter, explaining each derived status in plain language and giving direct usage examples. It also warns against pagination for farm-wide counts, indirectly guiding use of pagination parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with 'List MULTIPLE printers with optional filters', clearly stating a specific verb and resource. It also distinguishes itself from sibling tools like get_printer and get_farm_overview by name, placing it precisely in the tool family.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly instructs when not to use this tool: 'call get_printer instead' for single-printer details and 'call get_farm_overview instead' for farm-wide counts, adding 'do not list-then-filter' and 'do not paginate this'. It also provides concrete example status filters for common use cases.

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

All SimplyPrint: 3D Print Farm Management tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.1/5.0

Disambiguation3/5

Most tools are clearly separated by resource and action, but several overlapping queue-related tools exist—get_next_queue_item vs get_next_queue_items_for_printers, list_queue vs list_pending_queue_items, and inspect_printer_queue—which could cause misselection. list_custom_fields vs list_custom_fields_for and add_to_queue vs create_print_job add further ambiguity.

Naming Consistency4/5

Names overwhelmingly follow a verb_noun snake_case pattern with consistent resource nouns like print_job, queue_item, folder, and filament. Minor inconsistencies exist, such as add_to_queue vs create_folder/create_print_job, save_queue_group vs update/create, and the slightly odd home_printer and send_back_for_revision.

Tool Count1/5

With 74 tools, this is far beyond the recommended MCP server size and makes the toolset unwieldy to navigate, even for a broad domain. This clearly falls into the extreme 50+ tool category.

Completeness3/5

Core operational workflows—queue, print jobs, files, filament, and printer control—are well represented. However, printer lifecycle management is missing (no add/update/delete printer), and maintenance management is limited to a read-only dashboard with no corresponding actions.

list_printers

Input Schema

TDQS

Glama MCP Gateway

TDQS

Resources