Pingstack

Pause check

pause_check

DestructiveIdempotent

Pause a check. A paused check stops running or expecting heartbeats, opens no incidents and sends no alerts until it's resumed, so an outage during the pause goes unreported. Its history and settings are kept. Pausing a check that's already paused changes nothing. Needs the checks:pause permission, which is off unless granted when the connection is approved. Returns the check with status paused.

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

Input Schema

Name	Required	Description	Default
`id`	Yes	Check id (check_…).

Output Schema

Name	Required	Description	Default
`id`	Yes
`status`	Yes
`expires_on`	Yes
`configuration`	Yes
`dashboard_ids`	Yes
`status_reason`	Yes
`last_activity_at`	Yes
`notification_group_ids`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 10, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Goes well beyond the annotations: discloses that monitoring and heartbeat expectations stop, that incidents and alerts are suppressed, and that an outage during the pause goes unreported — a real consequence that explains why destructiveHint=true. It also states history/settings are preserved, that the call is idempotent in effect, that a checks:pause permission is required and often not granted, and what is returned.

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?

Five short sentences, each carrying distinct information: action, consequences, preservation, idempotency, permission, and return. The most consequential fact — that outages go unreported — is placed early rather than buried at the end.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 an output schema and safety annotations, nothing material is missing. Permissions, idempotency, side effects, and data preservation are all covered, and return values are summarized rather than over-explained.

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?

Only one parameter (id) with 100% schema description coverage, so the schema already fully documents it. The description adds no additional meaning about the id format or constraints, which is acceptable at this coverage level but earns only the baseline.

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 check') in the first two words, then defines the operational meaning: no runs, no heartbeats, no incidents, no alerts. The scope is unambiguous and an agent can distinguish it from resume_check, which the text implicitly references via 'until it's resumed'.

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?

Clearly establishes the context of use (silencing a noisy/monitored check temporarily while preserving history) and notes the no-op case for already-paused checks. It does not explicitly route the agent to resume_check for the inverse operation or warn about when pausing is a bad idea, so it stops short of full when/when-not guidance.

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

All Pingstack tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?