Skip to main content
Glama

SimplyPrint: 3D Print Farm Management

by io.simplyprint

list_queue

Read-onlyIdempotent

List print queue items with optional filters. Supports filtering by assigned printer(s), group, approval status, tags, queue-item custom-field values, and age. Example: older_than_days=7 for "items added more than 7 days ago", or custom_fields=[{id: "", value: "Engineering"}] for a specific department field.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
tagsNoMatch items that have any of the given tag names
groupNoOnly return items in this queue group (0 = the ungrouped bucket)
searchNoFilename substring search
compactNoKeep 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_byNoSort by this field. Default: sort_position (ascending — matches the queue's display order).
sort_dirNoSort direction; default asc.
page_sizeNoItems per page (1-200). Use this as the result-size cap.
printer_idNoOnly return queue items assigned to (via for_printers) any of these printer ids
added_afterNoItems created strictly after this ISO-8601 date
added_beforeNoItems created strictly before this ISO-8601 date
custom_fieldsNoFilter by custom field values. Each entry must specify the field id (uuid) and either value (exact match against string/number/boolean/date/options) or contains (case-insensitive substring on text fields). Multiple entries are AND-joined.
approval_statusNoFilter by approval status. Default excludes denied.
newer_than_daysNoItems created within the last this many days
older_than_daysNoItems created more than this many days ago

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safe-read nature is covered. The description adds filter capabilities and an example, but does not disclose additional behavior such as pagination, default sort, or compact-response implications beyond what the schema descriptions already state.

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 two sentences, front-loaded with the core action and then a dense but relevant example. There is no filler or redundant wording.

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 15-parameter schema with 93% coverage and strong annotations, the description provides enough orientation to select and begin using the tool. It does not explain response shape, but no output schema exists and invocation details are covered by the rich input schema.

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

Parameters3/5

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

Schema description coverage is 93%, so the schema carries most parameter meaning. The description's older_than_days and custom_fields example is useful but largely restates the schema's own parameter descriptions without adding significant new 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?

The description opens with 'List print queue items with optional filters', giving a clear verb, resource, and scope. It lists filtering dimensions, but does not explicitly distinguish itself from sibling tools like list_pending_queue_items or get_queue_item.

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?

The optional-filter framing and examples imply this is the general filtered-list tool, but there is no explicit when/when-not guidance or mention of alternatives. Given siblings like list_pending_queue_items and get_printer_queue, the usage context is only implicit.

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 toolsInspect
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.

Resources