Rolli MCP

resume_agent_schedule

Resume a paused Rolli Agent schedule so it runs again, with the next run time recalculated from the schedule's recurrence parameters.

Instructions

Resume a paused Rolli Agent schedule. next_run_at is recalculated based on the recurrence parameters.

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": "resume_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

A3.5/5.0

Behavior3/5

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

With no annotations at all, the description carries the full behavioral burden, and it does deliver one genuinely useful disclosure: next_run_at is recalculated from the recurrence parameters rather than resumed at the old time. It omits permission requirements, idempotency, and the error behavior for a non-paused schedule, which matter for a state-mutating call.

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 with zero filler; the operation is front-loaded and the side-effect note follows immediately. Nothing could be removed without losing information.

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 single-parameter state toggle with no output schema, an agent still needs to know what the call returns and how it behaves when the schedule is not paused; neither is addressed. The description is adequate to attempt the call but incomplete for predicting its outcome.

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 100% — the single `id` parameter is documented as "Schedule UUID" with a strict UUID pattern — so the schema already does the work. The description adds nothing about the identifier beyond what the schema states, which is acceptable at one parameter but earns no extra credit.

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 ("Resume") and a specific resource ("a paused Rolli Agent schedule"), which an agent can distinguish from pause_agent_schedule, delete_agent_schedule, or update_agent_schedule without opening the schema. It stops short of naming any sibling explicitly, so the differentiation is implicit rather than stated.

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 word "paused" implies the precondition for use, but the description never says what happens if the schedule is already active, nor does it point to pause_agent_schedule as the inverse operation or to update_agent_schedule when recurrence itself needs changing. Usage is inferable but not spelled out.

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