Skip to main content
Glama

Physical Capability Cloud

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

NameRequiredDescriptionDefault
jobIdYesJob ID to complete
messageNoCompletion message or notes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses irrecoverable side effects (scope revocation, escrow settlement in mock or real mode), the authentication requirement (API key or session key; cookie-only yields 403), and the exact failure codes 409 and 404 with their meanings. Annotations only say readOnlyHint=false and destructiveHint=false, so this added detail is essential and largely supplied.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the action and its effects, then error and authorization conditions, with no filler sentences. The error-code clauses are dense but each carries operational value; a slightly tighter phrasing of the 403/404 conditions would improve it marginally.

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 mutating, money-settling tool with no output schema, the description covers what the agent most needs: prerequisites, authorization, side effects, and error outcomes. Only the success payload shape is unstated, which is a minor omission given the rest of the coverage.

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 coverage is 100%, so jobId and message are already documented in the schema, and the description adds no format or constraint detail for either. The baseline of 3 applies when the schema does the explanatory work.

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?

States a specific verb ('Complete a job') plus the full sequence of effects — audit trail gathering, SHA-256 evidence bundle, evidence storage, scope revocation, escrow settlement. It also explicitly contrasts itself with operator_update_job_status, so an agent can distinguish it from the status-update sibling without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit when-not-to-use rule (a node that already submitted evidence and set status completed must not call it, since it will get 409) and names the sibling that covers that path. It also enumerates the allowed callers (buyer, kernel operator, gateway admin), so the agent can pre-check eligibility before invoking.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.