Skip to main content
Glama
Sign In
Pagerlane MCP Connector

Pagerlane MCP Connector

by si-essence
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

keep_acknowledge_alert

Idempotent

Acknowledge a Keep alert by fingerprint, preview the write unless confirm is true, and optionally let a new occurrence clear the status.

Instructions

Acknowledge an alert. POST /alerts/enrich?dispose_on_new_alert=true with enrichments status=acknowledged. Omit confirm for a dry-run preview. confirm must be the boolean true to execute.

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": {
      "fingerprint": "<fingerprint>"
    },
    "name": "keep_acknowledge_alert"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoSet to the boolean true to execute the write. Omit this field for a dry-run preview. false and the string true are rejected.
fingerprintYesKeep alert fingerprint.
dispose_on_new_alertNoKeep query flag. Defaults to true so a new occurrence can drop this status.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare a non-read-only, non-destructive, idempotent operation. The description goes further by revealing the exact mutation path (POST /alerts/enrich with status=acknowledged) and the preview-then-confirm safety protocol. It stops short of saying whether the acknowledgment can be undone or who is permitted to set it.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the action, then the mechanism, then the execution condition. The trailing confirm sentence duplicates the schema almost verbatim, which is the only real waste.

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 small mutating tool with annotations and full schema coverage, the essentials are present: what is written, via what endpoint, and what unlocks execution. An agent could call it correctly, though it lacks context on downstream effects of acknowledging an alert.

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 schema already documents confirm, fingerprint, and dispose_on_new_alert in detail. The description largely restates the confirm contract rather than adding new meaning, so baseline 3 applies.

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?

"Acknowledge an alert" names a specific verb and resource, and the endpoint detail pins down that it is a status write. It does not name the sibling it differs from (keep_resolve_alert, keep_enrich_alert), so an agent must infer which status-changing tool to pick.

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?

The dry-run/confirm mechanic is spelled out, which is real usage guidance for execution safety. But there is no statement of when to acknowledge versus resolve or enrich an alert, and no prerequisites such as required permissions.

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

Deploy Server

Other Tools