Skip to main content
Glama

pause_trigger

Idempotent

Pause a trigger: it stops checking at once and keeps where it got to. The playbooks that use it get nothing new until it is resumed. Use when stopping a misbehaving trigger.

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_trigger"
  }
}

Input Schema

NameRequiredDescriptionDefault
triggerIdYesThe trigger's id, from list_triggers or create_trigger.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare non-read-only, idempotent, and non-destructive, so the safety profile is covered. The description adds real context beyond that: state is preserved ("keeps where it got to"), downstream playbooks receive nothing new, and the effect is reversible on resume. It omits auth requirements and what happens to in-flight runs.

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 action and its immediate consequence, then downstream impact, then the use case. No redundant restatement of the name or schema.

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 mutation with annotations and no output schema, the description covers effect, scope of impact, state preservation, and reversibility. Only the return/error surface is left unstated, which is a minor gap for this complexity.

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 coverage is 100% and the single triggerId parameter is fully documented in the schema, including where to obtain it. The description adds no further meaning about the parameter, so 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 ("Pause a trigger") and immediately characterizes the effect: checking stops at once and the position is retained. The clause "until it is resumed" effectively distinguishes it from the resume sibling without ambiguity.

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?

Provides a clear situational trigger ("Use when stopping a misbehaving trigger") and implies the counterpart operation via "until it is resumed". It does not explicitly name resume_trigger or state when not to use it, so it stops short of full routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources