Skip to main content
Glama

SimplyPrint: 3D Print Farm Management

by io.simplyprint

get_next_queue_items_for_printers

Read-onlyIdempotent

Read-only preview: for each given printer, return the next queue item that would be started. Uses the same dedup matcher as create_print_job with next_queue_item=true, so the same queue item is never returned twice across printers in one call. Includes match failures per printer (issues) so you can explain why a printer has nothing to print. Does NOT start any job.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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.
printer_idYesComma-separated printer id(s). Does not need to be operational — offline printers return their would-be match too, so you can see what's waiting for them.

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, which the description reinforces. It adds valuable context beyond annotations: the dedup guarantee that the same queue item is never returned twice across printers, and the inclusion of match failures per printer. This is useful behavioral detail for a safe, idempotent operation.

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?

Three sentences, front-loaded with the essential action 'Read-only preview', and no filler. Every sentence adds value: what it does, the dedup behavior, and the failure reporting.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with only 2 params, no output schema, and clear annotations, the description covers the core behavior, important edge cases (offline printers, dedup), and the purpose of the returned issues. It is self-contained enough for an agent to select and invoke correctly.

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

Parameters4/5

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

Schema coverage is 100% with detailed parameter descriptions, so baseline is 3. The description adds extra context by explaining that printer_id accepts offline printers and that they return their would-be match, which is useful semantics not present in the schema.

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?

Description opens with 'Read-only preview' and clearly states the tool returns the next queue item that would be started for each given printer. It distinguishes from siblings like get_next_queue_item by explicitly mentioning batch processing across printers and the dedup matcher.

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

Usage Guidelines4/5

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

The description clearly implies a preview use-case ('Read-only preview', 'Does NOT start any job') and suggests a purpose ('so you can explain why a printer has nothing to print'). However, it does not explicitly name alternatives like the singular get_next_queue_item or state when not to use it.

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