ic_prints_update
ActiveTool of Immersive Commons
declared in 1.31.0
Move a print request through the farm lifecycle: pending -> accepted -> printing -> ready -> collected, or reject (from pending/accepted/printing) with a note. Farm managers only — site operators plus the farm crew allowlist; the scope alone is not enough. The requester is notified on every move. Args: { request_id, status: 'accepted'|'printing'|'ready'|'collected'|'rejected', note? }. Returns: { ok, request }. Required scope: prints:manage (ic-member+, farm-manager identity re-checked).
Parameters schema
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"request_id",
"status"
],
"properties": {
"note": {
"type": "string",
"maxLength": 2000,
"description": "Manager note (required advice for rejections — say why)."
},
"status": {
"enum": [
"accepted",
"printing",
"ready",
"collected",
"rejected"
],
"type": "string",
"description": "Target status. Must be a legal move from the current status."
},
"request_id": {
"type": "string",
"maxLength": 64,
"minLength": 1,
"description": "The request id (pj_...) to move."
}
}
}No endpoints wrapped at confidence ≥ 0.50.
Parent server
Immersive Commons
https://github.com/immersive-commons/ic-skills
1/7 registries