Rolli MCP

delete_agent_schedule

Permanently deletes a Rolli Agent schedule and its execution history, an irreversible action. Use pause instead to stop a schedule temporarily while keeping its history.

Instructions

Permanently delete a Rolli Agent schedule and its execution history. This is irreversible. Use pause_agent_schedule to temporarily stop a schedule without losing history.

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": "delete_agent_schedule"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Schedule 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

A4.3/5.0

Behavior4/5

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

No annotations exist, so the description carries the full burden; it discloses the two most important traits — permanence ('Permanently', 'This is irreversible') and collateral destruction of execution history. It does not mention permission requirements or what happens when the id does not exist, keeping it short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the destructive nature and irreversible consequence, followed by the alternative. No filler, though the 'Rolli Agent' qualifier is slightly redundant for an agent already in this toolset.

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 single-parameter destructive tool with no output schema, the description covers consequence, irreversibility, and the safe alternative. The only gap is behavior on an invalid or already-deleted id, which is a minor edge case given the simple schema.

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 and schema description coverage is 100%, so the schema already documents 'id' as a Schedule UUID. The description adds no format, source, or lookup guidance (e.g. where to obtain the schedule id) beyond what the schema provides, so the baseline 3 applies.

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 ('Permanently delete a Rolli Agent schedule') plus the extended scope ('and its execution history'), which an agent cannot infer from the name alone. It is clearly distinguishable from sibling update_agent_schedule and pause_agent_schedule.

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

Usage Guidelines5/5

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

Explicitly names the alternative (pause_agent_schedule) and the condition that selects it: temporarily stopping a schedule without losing history. This gives a direct when-to-use-this-vs-that routing rule.

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