Skip to main content
Glama

Pause a schedule

pause_schedule

Stops a schedule from firing while preserving its configuration and history, without confirmation. Restart it later with the resume action.

Instructions

Stops a schedule firing, keeping it and its history. No confirmation needed: stopping a runaway job should never be the harder thing to do. Use resume_schedule to start it again.

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

Input Schema

NameRequiredDescriptionDefault
triggerIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.53.0

TDQS

A4.1/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 disclose meaningful traits: state and history are preserved, the action is reversible via resume_schedule, and no confirmation step is required. It does not say what happens to an in-flight run, whether the caller needs specific permissions, or what error looks like for an unknown triggerId.

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 short sentences, front-loaded with the core effect followed by the safety guidance and the inverse operation. No sentence is filler and nothing is buried.

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, non-destructive state toggle with no output schema, this covers effect, reversibility, and the alternative well. The remaining gap is the undocumented triggerId and no word on how the paused state is reported back to the caller.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single required parameter, and the description never mentions triggerId at all — it never says the identifier refers to a schedule trigger rather than, say, a run or a workspace. The description does not compensate for the coverage gap, so the agent must infer the parameter's meaning from the field name alone.

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?

"Stops a schedule firing, keeping it and its history" gives a specific verb, a specific resource, and a scope qualifier that distinguishes it from a delete operation without naming one. An agent can tell what this does and what it does not do from the first sentence alone.

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 explicitly routes the agent to resume_schedule as the inverse operation and pre-empts a hesitation ("no confirmation needed"), which is real usage guidance. It stops short of stating when to pause versus delete_schedule, though "keeping it and its history" implies the distinction.

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