Skip to main content
Glama
Sign In
Rolli MCP

Rolli MCP

by rolliinc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

pause_agent_schedule

Pause a Rolli Agent schedule to stop execution while preserving the schedule and its history for later resumption.

Instructions

Pause a Rolli Agent schedule so it stops executing. The schedule and its history are preserved — resume it later with resume_agent_schedule.

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

Input Schema

NameRequiredDescriptionDefault
idYesSchedule UUID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.5.0
    • 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)$"
  2. Addedv1.3.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does address the two facts that matter most for a pause mutation: the schedule and its history are preserved (no data loss) and the change is reversible via resume_agent_schedule. Gaps remain: it does not say whether an already-paused schedule errors or is a no-op, whether an in-progress run is affected, or what permissions are required.

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 waste; the core action and effect are front-loaded, and the second sentence delivers the preservation/reversibility guarantee and the follow-up tool.

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 one-parameter mutation with no output schema and no annotations, the description covers purpose, the key side effect (preservation) and the reversal path, which is enough to invoke it correctly. It could be stronger by describing what is returned or the state transitions (paused vs. active), but nothing critical is missing for correct invocation.

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 ('Schedule UUID') is fully covered at 100%, so the schema already does the documenting. The description adds no extra meaning about the id (e.g., where to obtain it via list_agent_schedules), so the baseline of 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?

The description states a specific verb and resource ('Pause a Rolli Agent schedule') plus the immediate effect ('stops executing'), and it names the counterpart tool resume_agent_schedule, so the agent can distinguish it from resume/update/delete siblings without reading 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 Guidelines4/5

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

Usage is clear from the stated effect: use this to stop a schedule from running while keeping it. The description also points to resume_agent_schedule as the way back, which is the main alternative an agent would weigh. It stops short of explicit exclusions (e.g., use delete_agent_schedule if the schedule should be removed permanently, or cancel_agent_run for an in-flight run).

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

Deploy Server

Other Tools