Skip to main content
Glama
Sign In
Pagerlane MCP Connector

Pagerlane MCP Connector

by si-essence
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

keep_resolve_alert

Idempotent

Resolve a Keep alert by fingerprint; omit confirm for a dry-run preview, then set confirm to true to execute.

Instructions

Resolve an alert. POST /alerts/enrich?dispose_on_new_alert=true with enrichments status=resolved. 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_resolve_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.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, so the safety profile is partly covered. The description still adds real value by disclosing the two-phase dry-run/execute contract and the strictness of confirm (boolean true only, false and the string 'true' rejected), which is behavior not derivable from the annotations.

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 and endpoint before the confirm caveat. Slight redundancy between the description's confirm sentence and the schema's identical description, but nothing wasteful enough to penalize heavily.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a state-changing tool with no output schema, the description does not say what a dry-run preview returns or what happens if the fingerprint does not exist or is already resolved. Annotations cover the mutation and idempotency profile, but the response shape and failure behavior remain unspecified.

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 description coverage is 100%, so the schema already documents all three parameters including confirm's dry-run semantics and dispose_on_new_alert's default. The description largely restates the confirm parameter rather than adding new meaning, so the 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?

"Resolve an alert" is a specific verb+resource, and the endpoint detail (POST /alerts/enrich with status=resolved) makes the mechanic concrete. It does not explicitly distinguish itself from the sibling keep_acknowledge_alert or keep_enrich_alert, so an agent must infer that 'resolve' is the terminal disposal state rather than acknowledgement.

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?

Gives clear operational guidance for the confirm flag: omit it for a dry-run preview, set it to boolean true to execute. It does not say when to choose this over keep_acknowledge_alert or keep_enrich_alert, so sibling routing is left to inference.

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