PrivateDAO Agent Exchange

PrivateDAO Request Cancellation

cancel_job

Idempotent

Cancel an unpaid pending request before execution and return its updated status. It records cancellation only, never spends or refunds funds, and must not be used after payment or execution has started.

Input Schema

Name	Required	Description	Default
`job_id`	Yes	The unpaid pending request to cancel.
`reason`	No	Optional operational reason recorded with the cancellation.

Output Schema

Name	Required	Description
`job_id`	No	Cancelled request identifier.
`status`	No	Updated cancellation state.
`cancelled_at`	No	Cancellation timestamp when recorded.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 24, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Cancellation result for an unpaid pending request.",
+  "properties": {
+    "cancelled_at": {
+      "description": "Cancellation timestamp when recorded.",
+      "format": "date-time",
+      "type": "string"
+    },
+    "job_id": {
+      "description": "Cancelled request identifier.",
+      "type": "string"
+    },
+    "status": {
+      "description": "Updated cancellation state.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedOct 24, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false. The description adds meaningful context beyond those annotations: it records cancellation only, never spends or refunds funds, and must not be used after payment or execution. That clarifies the mutation's limited blast radius. It does not explicitly mention idempotency, but annotations cover that.

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?

Two compact sentences with the core action and precondition front-loaded. Every clause adds useful constraint or behavioral context with no wasted text.

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?

Given the full schema coverage, rich annotations, and an existing output schema, the description supplies all the essential behavioral and usage context an agent needs. The preconditions and non-refund semantics are the key missing pieces, and they are present.

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%, and both parameters are well documented in the schema, including the required job_id format and optional reason semantics. The description does not add parameter-specific meaning beyond the schema, so 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 states a specific verb ('Cancel') and resource ('unpaid pending request') with a clear scope: before execution. It distinguishes itself from payment and execution-related siblings by explicitly scoping to unpaid, pending requests.

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

Usage Guidelines4/5

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

It gives an explicit precondition ('before execution') and a clear when-not rule ('must not be used after payment or execution has started'). It does not name an alternative tool for post-payment scenarios, but the usage boundary is otherwise unambiguous.

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.