Skip to main content
Glama

SimplyPrint: 3D Print Farm Management

by io.simplyprint

cancel_print

Destructive

Cancel the current print on a printer

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reasonNoCancel reason ID. May be required depending on organization settings.
commentNoOptional comment explaining why the print was cancelled. May be required depending on organization settings.
printer_idYesThe printer IDs (comma-separated for multiple)
custom_positionNoCustom sort position when return_position is 'custom'.
return_positionNoPosition to insert queue item at when returning to queue (original, top, bottom or custom).
return_to_queueNoWhether to return cancelled queued print to the queue. Uses organization default if not specified.

TDQS

B3.2/5.0
Behavior2/5

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

Annotations declare destructiveHint=true and readOnlyHint=false, but the description adds no further behavioral context. It does not mention irreversibility, possible return-to-queue behavior (though schema hints at it), or other side effects, leaving the agent unaware of consequences beyond the basic action.

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, clear sentence with no filler or redundancy. It is appropriately sized for a tool whose schema already provides detailed parameter information.

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?

With six parameters, no output schema, and a destructive action, the description is significantly under-specified. It does not explain how cancellation affects the print job, when reason/comment might be required, or the implications of return_to_queue, making it incomplete for an agent to fully understand usage.

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 100%, so all six parameters are already documented with descriptions. The tool description itself does not add any parameter meaning, so the baseline of 3 is appropriate.

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 clearly states the action ('Cancel') and the target ('the current print on a printer'), which distinguishes it from siblings like pause_print or archive_print_job. It uses a specific verb and resource, making the tool's intent immediately obvious.

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?

No guidance is provided on when to use this tool versus alternatives such as pause_print or delete_queue_item. It does not mention prerequisites, exclusions, or scenarios where another tool might be more appropriate.

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