Skip to main content
Glama
Sign In
Pagerlane MCP Connector

Pagerlane MCP Connector

by si-essence
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

keep_list_alerts

Read-only

Lists recent Keep alerts from the self-hosted Keep API, letting you set a maximum result count to review cached alert data for triage and monitoring.

Instructions

List the latest Keep alerts. GET /alerts with limit (Keep default 1000). Cached reads. Auth is the X-API-KEY header.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "keep_list_alerts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum alerts to return. Keep default is 1000.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds two genuinely useful traits beyond that: cached reads and X-API-KEY header auth, plus the Keep default limit of 1000. It says nothing about pagination, ordering of 'latest', or cache staleness, so it's adequate but not rich.

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 front-loaded fragments: purpose, endpoint plus limit, caching, auth. Every clause carries information and nothing is padded. Fragments rather than sentences slightly hurt readability but not efficiency.

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 read-only list tool with no output schema, the definition covers purpose, endpoint, default, caching, and auth, which is close to everything an agent needs. Missing only pagination behavior and a pointer to the filtered alternatives in a crowded sibling set.

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 parameter's description already states the Keep default of 1000 and its range. The description only repeats the default, adding no syntax or semantics beyond the schema, 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?

The description states a specific verb and resource ('List the latest Keep alerts') and pins down the endpoint 'GET /alerts'. It doesn't distinguish itself from sibling keep_search_alerts or keep_list_workflows, so it stops short of a 5.

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?

Usage is only implied: listing the latest alerts at the default limit suggests a broad, unfiltered pull, which implicitly points agents to keep_search_alerts for filtered queries, but that alternative is never named. There is no explicit when-to-use or when-not-to-use statement.

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