Ausca

Request bounded cancellation

ausca_cancel_invocation

DestructiveIdempotent

Request bounded cancellation of one invocation. Cancellation is idempotent, may be refused, and may lose a race with terminal completion.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`invocation_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 24, 2026

changedOutput schema / oneOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "invocation": {
-        "$ref": "#/$defs/InvocationState"
-      },
-      "status": {
-        "enum": [
-          "cancellation_requested",
-          "already_terminal"
-        ],
-        "type": "string"
-      }
-    },
-    "required": [
-      "status",
-      "invocation"
-    ],
-    "type": "object"
-  },
-  {
-    "$ref": "#/$defs/RefusedResult"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "invocation": {
+        "$ref": "#/$defs/InvocationState"
+      },
+      "status": {
+        "enum": [
+          "cancellation_requested"
+        ],
+        "type": "string"
+      }
+    },
+    "required": [
+      "status",
+      "invocation"
+    ],
+    "type": "object"
+  },
+  {
+    "$ref": "#/$defs/RefusedResult"
+  }
+]

Changed7 schema fields changedSep 18, 2026
- addedOutput schema / $defs / ArtifactRef / description
```
Added value: +"Opaque artifact reference minted by artifact commitment. Relay it unchanged; its form is not part of the contract."
```
- addedOutput schema / $defs / ArtifactRef / maxLength
```
Added value: +512
```
- addedOutput schema / $defs / ArtifactRef / minLength
```
Added value: +1
```
- removedOutput schema / $defs / ArtifactRef / pattern
```
Removed value: -"^runx:artifact:sha256:[a-f0-9]{64}$"
```
- addedOutput schema / $defs / ReceiptReference / properties / uri / description
```
Added value: +"Opaque receipt identity minted by the notary. Relay it unchanged; its form is not part of the contract."
```
- changedOutput schema / $defs / ReceiptReference / properties / uri / minLength
```
Previous value: -14New value: +1
```
- removedOutput schema / $defs / ReceiptReference / properties / uri / pattern
```
Removed value: -"^runx:receipt:.+$"
```

Changed6 schema fields changedSep 7, 2026

addedOutput schema / $defs / ArtifactEvidence

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "artifact_ref": {
+      "$ref": "#/$defs/ArtifactRef"
+    },
+    "content_digest": {
+      "$ref": "#/$defs/Digest"
+    },
+    "created_at": {
+      "format": "date-time",
+      "type": "string"
+    },
+    "media_type": {
+      "maxLength": 200,
+      "minLength": 1,
+      "type": "string"
+    },
+    "size_bytes": {
+      "maximum": 26214400,
+      "minimum": 1,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "artifact_ref",
+    "content_digest",
+    "media_type",
+    "size_bytes",
+    "created_at"
+  ],
+  "type": "object"
+}

addedOutput schema / $defs / ArtifactRef

Added value: +{
+  "pattern": "^runx:artifact:sha256:[a-f0-9]{64}$",
+  "type": "string"
+}

addedOutput schema / $defs / InvocationFailure

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "code": {
+      "maxLength": 96,
+      "minLength": 1,
+      "type": "string"
+    },
+    "message": {
+      "maxLength": 500,
+      "minLength": 1,
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}

addedOutput schema / $defs / InvocationState / properties / failure
```
Added value: +{
+  "$ref": "#/$defs/InvocationFailure"
+}
```
addedOutput schema / $defs / InvocationState / properties / output_artifact
```
Added value: +{
+  "$ref": "#/$defs/ArtifactEvidence"
+}
```

addedOutput schema / $defs / ReceiptReference / properties / public_url

Added value: +{
+  "description": "Unguessable public verification page for the privacy-bounded hash-only proof. It reveals the receipt digest, service, public price, and completion time, but not input bytes, output bytes, or their content digests.",
+  "format": "uri",
+  "maxLength": 2048,
+  "pattern": "^https://[^?#]+/r/[a-f0-9]{64}$",
+  "type": "string"
+}

Changed1 schema field changedSep 7, 2026

removedOutput schema / $defs / ReceiptReference / properties / public_url

Removed value: -{
-  "description": "Unguessable public verification page for the privacy-bounded hash-only proof. It reveals the receipt digest, service, public price, and completion time, but not input bytes, output bytes, or their content digests.",
-  "format": "uri",
-  "maxLength": 2048,
-  "pattern": "^https://[^?#]+/r/[a-f0-9]{64}$",
-  "type": "string"
-}

Changed1 schema field changedSep 3, 2026

addedOutput schema / $defs / ReceiptReference / properties / public_url

Added value: +{
+  "description": "Unguessable public verification page for the privacy-bounded hash-only proof. It reveals the receipt digest, service, public price, and completion time, but not input bytes, output bytes, or their content digests.",
+  "format": "uri",
+  "maxLength": 2048,
+  "pattern": "^https://[^?#]+/r/[a-f0-9]{64}$",
+  "type": "string"
+}

First observedSep 1, 2026

TDQS

A4/5.0

Behavior4/5

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

The description augments the annotations by revealing that cancellation is bounded, may be refused, and can lose a race with terminal completion. It also restates idempotence, which matches idempotentHint=true. No contradiction exists.

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 short sentences front-load the action and then supply the key behavioral caveats. Every sentence earns its place with zero redundancy.

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?

For a one-parameter cancellation with an output schema and annotations covering readOnly/destructive/idempotent, the description covers the critical uncertainty (refusal/race). A slightly more explicit statement about when cancellation is appropriate would make it complete, but nothing essential is missing.

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 0%, so the description must carry parameter meaning. It clarifies the target is 'one invocation' and the only parameter is invocation_id, but it does not explain identifier format or requiredness beyond the schema's own pattern.

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 uses a specific verb-resource pair ('cancel... one invocation') and the title reinforces the bounded, best-effort nature. No sibling tool performs cancellation, so it is immediately distinguishable from get/prepare/search tools.

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

Usage Guidelines3/5

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

Usage context is implied: call this when an invocation should be cancelled. However, it does not state conditions for choosing cancellation over waiting or polling, nor does it identify alternatives/exclusions relative to sibling tools.

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

All Ausca 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.