CueFrame

Cancel Compose

cancel_compose

Idempotent

Cancel an in-flight compose job (stop a runaway/mis-priced ensemble). Needs projectId + composeJobId (from compose). The director cancel is confirmed before the row flips; any linked charge is released. No-op-reject (422) if already terminal.

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": {
      "projectId": "<projectId>",
      "composeJobId": "<composeJobId>"
    },
    "name": "cancel_compose"
  }
}

Input Schema

Name	Required	Description
`commandId`	No	Retry identity. A call repeated with the same commandId returns the first result instead of acting twice.
`projectId`	Yes	projectId (path).
`composeJobId`	Yes	composeJobId (path).

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 28, 2026
- addedInput schema / $defs
```
Added value: +{
+  "__schema0": {
+    "maxLength": 128,
+    "minLength": 1,
+    "type": "string"
+  }
+}
```
- addedInput schema / properties / commandId / $ref
```
Added value: +"#/$defs/__schema0"
```
- removedInput schema / properties / commandId / maxLength
```
Removed value: -128
```
- removedInput schema / properties / commandId / minLength
```
Removed value: -1
```
- removedInput schema / properties / commandId / type
```
Removed value: -"string"
```

Changed1 schema field changedOct 22, 2026

addedInput schema / properties / commandId

Added value: +{
+  "description": "Retry identity. A call repeated with the same commandId returns the first result instead of acting twice.",
+  "maxLength": 128,
+  "minLength": 1,
+  "type": "string"
+}

First observedOct 10, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly=false, destructive=false, idempotent=true, so the safety profile is covered. The description adds real value beyond that: the director cancel is confirmed before the row flips, linked charges are released, and an already-terminal job returns 422 rather than silently succeeding — behavior an agent could not infer from annotations.

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?

Four short sentences, front-loaded with the action and the motivating scenario, then prerequisites, then side effects, then the failure mode. Nothing is redundant with the schema or the title.

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 cancel mutation with no output schema, the description covers prerequisites, side effects (charge release), and the terminal-state error. It does not say what state the job ends in or how to confirm the cancellation afterward, a minor gap given there is no return-value documentation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds provenance the schema lacks ('composeJobId from compose'), which directly helps an agent source the required ID. commandId's retry semantics are left entirely to the schema.

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 ('Cancel an in-flight compose job') and glosses the intent ('stop a runaway/mis-priced ensemble'). The resource is unambiguous against siblings like cancel_export, cancel_render, and cancel_job, which operate on different object types.

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?

Gives a clear use condition (stopping a runaway or mis-priced job) and notes the terminal-state case that will be rejected with 422. It stops short of naming an explicit alternative or explaining what to do instead when the job is already terminal, so it falls short of a 5.

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

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