pcc_job_complete
Complete a job: gathers tool call audit trail from execution scopes, builds evidence bundle with SHA-256 hash, stores evidence, revokes scopes, and settles escrow (mock or real). This is how a job run through execution scopes is finished. A node that submitted its evidence and set status completed (operator_update_job_status) must not call it: it then answers 409 ("Job already completed or completion in progress"). Only the job's buyer, its kernel's operator or the gateway admin may call it: a buyer or operator must send an API key or session key in the Authorization header (a sign-in cookie alone gets 403), and any other proven wallet gets 404 ("Job not found").
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"jobId": "<jobId>"
},
"name": "pcc_job_complete"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| jobId | Yes | Job ID to complete | |
| message | No | Completion message or notes |