PrivateDAO Agent Exchange

PrivateDAO Paid Workflow Payment

privatepay_job_payment

Destructive

Apply a finalized PrivatePAY x402 payment to an existing paid job and execute it once. Use this instead of submit_payment for a job created with payment_mode=privatepay; it consumes supplied payment proof, may settle funds, and returns workflow evidence.

Input Schema

Name	Required	Description	Default
`job_id`	Yes	Job identifier returned by create_paid_job.
`payment_signature`	Yes	The x402 PAYMENT-SIGNATURE value returned by the paying agent wallet.

Output Schema

Name	Required	Description
`job_id`	No	Paid workflow job identifier.
`result`	No	Service result when execution completes.
`status`	No	Job or payment state after applying the supplied x402 proof.
`receipt`	No	Public evidence receipt when execution completes.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 1, 2026

addedInput schema / properties / job_id / description

Added value: +"Job identifier returned by create_paid_job."

addedOutput schema / properties

Added value: +{
+  "job_id": {
+    "description": "Paid workflow job identifier.",
+    "type": "string"
+  },
+  "receipt": {
+    "additionalProperties": true,
+    "description": "Public evidence receipt when execution completes.",
+    "type": "object"
+  },
+  "result": {
+    "additionalProperties": true,
+    "description": "Service result when execution completes.",
+    "type": "object"
+  },
+  "status": {
+    "description": "Job or payment state after applying the supplied x402 proof.",
+    "type": "string"
+  }
+}

Changed2 schema fields changedOct 28, 2026

removedInput schema / properties / job_id / description

Removed value: -"Job identifier returned by create_paid_job."

removedOutput schema / properties

Removed value: -{
-  "job_id": {
-    "description": "Paid workflow job identifier.",
-    "type": "string"
-  },
-  "receipt": {
-    "additionalProperties": true,
-    "description": "Public evidence receipt when execution completes.",
-    "type": "object"
-  },
-  "result": {
-    "additionalProperties": true,
-    "description": "Service result when execution completes.",
-    "type": "object"
-  },
-  "status": {
-    "description": "Job or payment state after applying the supplied x402 proof.",
-    "type": "string"
-  }
-}

Changed2 schema fields changedOct 28, 2026

addedInput schema / properties / job_id / description

Added value: +"Job identifier returned by create_paid_job."

addedOutput schema / properties

Added value: +{
+  "job_id": {
+    "description": "Paid workflow job identifier.",
+    "type": "string"
+  },
+  "receipt": {
+    "additionalProperties": true,
+    "description": "Public evidence receipt when execution completes.",
+    "type": "object"
+  },
+  "result": {
+    "additionalProperties": true,
+    "description": "Service result when execution completes.",
+    "type": "object"
+  },
+  "status": {
+    "description": "Job or payment state after applying the supplied x402 proof.",
+    "type": "string"
+  }
+}

Changed2 schema fields changedOct 28, 2026

removedInput schema / properties / job_id / description

Removed value: -"Job identifier returned by create_paid_job."

removedOutput schema / properties

Removed value: -{
-  "job_id": {
-    "description": "Paid workflow job identifier.",
-    "type": "string"
-  },
-  "receipt": {
-    "additionalProperties": true,
-    "description": "Public evidence receipt when execution completes.",
-    "type": "object"
-  },
-  "result": {
-    "additionalProperties": true,
-    "description": "Service result when execution completes.",
-    "type": "object"
-  },
-  "status": {
-    "description": "Job or payment state after applying the supplied x402 proof.",
-    "type": "string"
-  }
-}

Changed1 schema field changedOct 26, 2026

addedOutput schema / properties

Added value: +{
+  "job_id": {
+    "description": "Paid workflow job identifier.",
+    "type": "string"
+  },
+  "receipt": {
+    "additionalProperties": true,
+    "description": "Public evidence receipt when execution completes.",
+    "type": "object"
+  },
+  "result": {
+    "additionalProperties": true,
+    "description": "Service result when execution completes.",
+    "type": "object"
+  },
+  "status": {
+    "description": "Job or payment state after applying the supplied x402 proof.",
+    "type": "string"
+  }
+}

Changed1 schema field changedOct 25, 2026
- addedInput schema / properties / job_id / description
```
Added value: +"Job identifier returned by create_paid_job."
```

Changed1 schema field changedOct 24, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Private payment application result for a selected job.",
+  "type": "object"
+}

AddedOct 22, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and readOnlyHint=false, so the risk profile is known. The description adds real value beyond that: it consumes supplied payment proof, may settle funds, executes only once, and returns workflow evidence. It stops short of saying what a retry does after a partial settlement or what failure leaves behind, which matters for a non-idempotent money-moving call.

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?

One dense sentence, front-loaded with the action and followed immediately by the sibling routing rule. Every clause contributes: the action, the alternative, the mode condition, the side effects, and the return shape.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values ('workflow evidence') need only be gestured at, and the description does that. For a destructive, non-idempotent payment-settlement call, the main remaining gap is post-failure or duplicate-submission behavior, which the description does not address despite saying 'execute it once.'

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%, including provenance ('returned by create_paid_job') and the x402 PAYMENT-SIGNATURE origin, so the schema carries the parameter burden. The description adds only the notion of 'supplied payment proof' being consumed, which is a restatement rather than new syntax or format detail. Baseline 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 opens with a specific verb and resource: 'Apply a finalized PrivatePAY x402 payment to an existing paid job and execute it once.' It names the sibling it replaces (submit_payment) and the discriminating job attribute (payment_mode=privatepay), so the agent can tell it apart from submit_payment 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?

It states the selection condition explicitly ('for a job created with payment_mode=privatepay') and names the alternative it substitutes ('Use this instead of submit_payment'). There is essentially no inference needed to route between this and submit_payment.

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

All PrivateDAO Agent Exchange tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

PrivateDAO Paid Workflow Payment

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources