Rolli MCP

cancel_agent_run

Cancel a pending or running Rolli Agent run by UUID and mark it as failed. Use this to stop active or queued runs that should not continue.

Instructions

Cancel a pending or running Rolli Agent run. Marks the run as failed.

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": {
      "id": "<id>"
    },
    "name": "cancel_agent_run"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Run UUID

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.5.0Nov 4, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

addedInput schema / properties / id / pattern

Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"

Addedv1.3.0Jun 3, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden. It does usefully disclose the post-condition ('Marks the run as failed'), but omits whether cancellation is immediate or cooperative, whether it is reversible or the run can be rerun, and what happens to partial output. Those gaps matter for a mutation tool with zero annotation coverage.

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-loaded with the action and scope, then the side effect. Nothing is wasted and nothing needs reordering.

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

Completeness3/5

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

For a one-parameter mutation tool with no annotations and no output schema, the definition covers the action, the eligible states, and the resulting status. It still leaves an agent guessing about irreversibility and about how to obtain a valid run id, which is the main remaining gap.

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?

There is a single required parameter whose schema description ('Run UUID') and regex pattern already document it fully at 100% coverage. The description adds no format or sourcing guidance (e.g. obtainable from list_agent_runs), so it matches the baseline of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Cancel a ... Rolli Agent run') and scopes it to 'pending or running' runs, which separates it from delete_agent_run on state grounds. It does not name the sibling it differs from, so an agent must infer the distinction from sibling names alone.

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?

The phrase 'pending or running' implies a state precondition, giving some implicit guidance on when the tool applies. However, it never says when to prefer this over delete_agent_run or update_agent_run, nor what to do for a completed run.

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