Skip to main content
Glama

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

NameRequiredDescriptionDefault
invocation_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • removedOutput schema / $defs / ArtifactEvidence / properties / artifact_ref
      Removed value: -{
      -  "$ref": "#/$defs/ArtifactRef"
      -}
    • addedOutput schema / $defs / ArtifactEvidence / properties / artifact_uri
      Added value: +{
      +  "$ref": "#/$defs/ArtifactUri"
      +}
    • changedOutput schema / $defs / ArtifactEvidence / required
      Previous value: -[
      -  "artifact_ref",
      -  "content_digest",
      -  "media_type",
      -  "size_bytes",
      -  "created_at"
      -]New value: +[
      +  "artifact_uri",
      +  "content_digest",
      +  "media_type",
      +  "size_bytes",
      +  "created_at"
      +]
    • removedOutput schema / $defs / ArtifactRef
      Removed value: -{
      -  "description": "Opaque artifact reference minted by artifact commitment. Relay it unchanged; its form is not part of the contract.",
      -  "maxLength": 512,
      -  "minLength": 1,
      -  "type": "string"
      -}
    • addedOutput schema / $defs / ArtifactUri
      Added value: +{
      +  "description": "Opaque artifact reference minted by artifact commitment. Relay it unchanged; its form is not part of the contract.",
      +  "maxLength": 512,
      +  "minLength": 1,
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • 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"
      +  }
      +]
  3. Changed7 schema fields changed
    • 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:.+$"
  4. Changed6 schema fields changed
    • 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"
      +}
  5. Changed1 schema field changed
    • 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"
      -}
  6. Changed1 schema field changed
    • 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"
      +}
  7. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true, so repeating idempotency earns nothing, but the description adds genuinely new behavior: cancellation may be refused and may race against terminal completion, which tells the agent the outcome is not guaranteed. It does not say what work is discarded despite destructiveHint=true, nor what refusal looks like.

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 sentences, zero filler, with the identification of the operation and its outcome caveats front-loaded.

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 shape needn't be explained, and annotations carry the safety profile (destructive, open-world). The description covers the surprising semantics of an unreliable cancellation; only authorization requirements and the fate of in-flight work are 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?

Only one parameter with 0% schema description coverage, so the description must compensate; it clarifies that exactly one invocation is targeted (no batch or list form), which is useful. It adds nothing about the identifier itself, though the schema pattern and length constraints document the format.

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 and resource ('cancellation of one invocation') and adds a meaningful qualifier ('bounded'), which no sibling tool carries. An agent can tell this apart from ausca_get_invocation or ausca_prepare_invocation without consulting the schema.

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?

'of one invocation' implies the scope is a single target rather than a batch, and 'may be refused' hints at preconditions, but there is no explicit when-to-use versus when-to-use-an-alternative guidance and no stated prerequisites.

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.