Skip to main content
Glama

Resume a paused schedule

resume_schedule

Resumes a paused schedule and clears its failure count, requiring confirmation before re-enabling unattended runs.

Instructions

Starts a paused schedule again and clears its failure count. Requires confirm=true — this is the moment code begins running unattended again. If it was auto-paused (five consecutive failures, or an exhausted quota), fix the cause first: resuming a broken job just burns the quota again and re-pauses it.

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": {
      "triggerId": "<triggerId>"
    },
    "name": "resume_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to resume. Omit/false returns a preview only.
triggerIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.53.0

TDQS

A4.4/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 does well: it discloses that failure counts are reset, that confirm=true is mandatory for the real action, that omitted/false yields a preview, and that resuming means code runs unattended again. It does not mention permission requirements or what happens if the schedule is already running, so it falls one step short of complete.

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?

Three sentences, front-loaded with the action, then the hard gate, then the risk warning. Every sentence adds distinct operational value, with no restatement of the name or 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 two-parameter mutation with no annotations and no output schema, the description supplies purpose, precondition, safety gate, and failure-mode warning. Remaining gaps (auth requirements, behavior on an already-active schedule, return shape) are modest.

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 50%: confirm is documented in the schema, triggerId is not. The description compensates by tying confirm to a meaningful consequence (the point where unattended execution resumes) and by referring to the target schedule's failure count, though it never explains triggerId's identity or range in prose.

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?

"Starts a paused schedule again and clears its failure count" pairs a specific verb with a specific resource and adds a secondary side effect, so an agent knows precisely what state transition occurs. The stated precondition (must be paused) makes it trivially distinguishable from pause_schedule.

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?

It establishes the when (a paused schedule) and, unusually, an explicit when-not: do not resume until an auto-pause cause (five consecutive failures or exhausted quota) is fixed. It stops short of naming a sibling alternative, but the caution around resuming a broken job gives concrete situational guidance.

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