Queue a print

Help the user queue a print on their SimplyPrint farm. The file argument may be a local path, an API file id (hex hash), a SimplyPrint user-file UID, or a file name already in the user's library.

Steps:

1. Decide the file source. Treat the argument as a local path if any of the following is true:

• It contains / or \.
• It starts with ./, ../, ~, or a Windows drive letter (e.g. C:\).
• It resolves to an existing file on disk.

Otherwise, treat it as an existing SimplyPrint file (numeric UserFile id, UUID, API file hex hash, or name to look up with list_files).

1. Pick the queue group. If the user didn't name one, list groups with list_queue_groups and ask. The MCP add_to_queue tool needs a group id.

1. Resolve custom fields. If the user used with <k>=<v>, <k>=<v> syntax, call list_custom_fields_for with category: "print", subCategory: "print_queue" (lowercase!) to map human names to their string fieldId UUIDs. Build the backend submission array: [{"customFieldId":"<uuid>","value":{"string":"..."}}].

1. If local, upload first using the helper:

• Bash / Git Bash: ${CLAUDE_PLUGIN_ROOT}/scripts/upload.sh --file <path>
• Windows PowerShell 7+: ${CLAUDE_PLUGIN_ROOT}/scripts/upload.ps1 -File <path>

Parse stdout FILE_ID=<hex-hash>. Then call MCP add_to_queue with fileId: <hash>, group: <id>, and any custom fields.

1. If the file is already in SimplyPrint:

• If it's an API file hex hash, call add_to_queue with fileId: <hash>.
• If it's a user-file UID (32-hex from the library), call add_to_queue with filesystem: <uid> (or its numeric row id).
• If it's a file name, look it up with list_files first.

1. Confirm back: file name, queue group, queue item id (from created_id in the response), queue position. Include a panel URL (https://simplyprint.io/panel/queue).

If the user wants to print immediately rather than queue, use start-print instead. If the user already has a queue item id and just wants to start it on a printer, pass --queue-item-id to print.sh / -QueueItemId to print.ps1.

Never start a print on a printer that's reporting an error or offline state — surface the error to the user instead.