Skip to main content
Glama
Sign In
Pagerlane MCP Connector

Pagerlane MCP Connector

by si-essence
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

keep_get_incident

Read-only

Retrieve a single incident by its UUID, with optional inclusion of related alerts for incident investigation and response.

Instructions

Get one incident by UUID. GET /incidents/{incident_id}. Optional include_alerts also calls GET /incidents/{incident_id}/alerts.

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": {
      "incident_id": "<incident_id>"
    },
    "name": "keep_get_incident"
  }
}

Input Schema

NameRequiredDescriptionDefault
incident_idYesKeep incident UUID.
alerts_limitNo
alerts_offsetNo
include_alertsNoIf true, also GET /incidents/{id}/alerts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/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 the safety profile is covered. The description adds genuinely useful behavior beyond that: include_alerts triggers a second request to GET /incidents/{id}/alerts, which tells the agent the call has a side cost. It stops short of describing how alerts_limit/alerts_offset behave or what the response contains.

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 core action, with zero filler. The literal REST path in sentence two is largely redundant with sentence one, which is the only wasted space.

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 simple single-record getter with annotations and no output schema, most of what an agent needs is present. However, half the parameters (the alerts pagination pair) are unexplained in both schema and description, leaving a real gap for a 4-parameter tool.

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 coverage is only 50%: incident_id and include_alerts are documented inline, but alerts_limit and alerts_offset have no descriptions anywhere. The description does not explain that these two parameters page the embedded alerts, so an agent cannot tell whether they are ignored without include_alerts=true or what units they use.

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?

States a specific verb and resource: "Get one incident by UUID", and the singular framing implicitly separates it from keep_list_incidents. It does not explicitly name any sibling, so the differentiation is inferable 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?

Usage is implied by the required UUID parameter and the single-record scope, but there is no explicit guidance on when to prefer this over keep_list_incidents or keep_search_alerts. No exclusions or prerequisites are given.

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