Skip to main content
Glama

Resume an alert

resume_alert

Resume only the connected owner's paused alert. Requires alerts:write and a paid plan; no paused-period backlog is sent.

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

Input Schema

NameRequiredDescriptionDefault
idYes

Output Schema

NameRequiredDescriptionDefault
confirmationNo
subscriptionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the annotations (which only declare non-readonly, non-idempotent, non-destructive), the description adds two substantive facts: the alerts:write scope and paid-plan prerequisite, and the key behavioral caveat that no paused-period backlog is delivered on resume. That caveat is exactly the kind of side effect an agent cannot infer from structured fields. It stops short of saying what a repeat resume on an already-active alert returns, which matters given idempotentHint=false.

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 tight sentences with the ownership constraint front-loaded and the prerequisites and caveat following in priority order. Every clause carries distinct information; nothing is redundant with the 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 one-parameter state-changing tool with annotations and an output schema, the description covers the permissions model, plan gating, and the most important behavioral surprise. The remaining gap is the unexplained id parameter and the result of resuming an already-active alert.

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% and the sole parameter, id, is never mentioned in the description, so nothing is added about its meaning or accepted format (the schema only supplies a pattern and length bounds). The identifier is guessable from context, which prevents a 1, but the description does not compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ("Resume ... paused alert") plus a scope qualifier ("only the connected owner's"), which clearly separates it from unrelated siblings. It never names the obvious counterpart pause_alert, so the reverse-operation relationship is left implicit rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

"Resume only the connected owner's paused alert" implies the precondition (the alert must be paused and owned by the caller) and implicitly routes agents away from pause_alert. However, there is no explicit when-not guidance, no named alternative for unpausing another user's alert, and no statement of what happens when the alert isn't paused.

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