PingRelay MCP Server

incident_get

Read-onlyIdempotent

Get one non-deleted incident summary by external GUID in the authenticated organization, including description, details, severity, assignee, and affected service. Use IncidentAlertHistory for delivery records.

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": {
      "incidentExternalId": "<incidentExternalId>"
    },
    "name": "incident_get"
  }
}

Input Schema

Name	Required	Description	Default
`incidentExternalId`	Yes	External incident GUID returned as Id by IncidentList, MonitorIncidents, or HeartbeatIncidents.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 8, 2026

addedInput schema / properties / incidentExternalId / description

Added value: +"External incident GUID returned as Id by IncidentList, MonitorIncidents, or HeartbeatIncidents."

First observedNov 7, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so safety is covered. The description adds two things annotations cannot: it filters out soft-deleted incidents and restricts results to the caller's organization, which tells the agent why a valid GUID might return nothing and that no cross-org access occurs. It says nothing about the not-found/deleted response shape.

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 sentences, front-loaded with the core operation and scope, with the second sentence doing distinct routing work. Nothing is redundant or padded.

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

Completeness5/5

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

For a single-parameter read tool with rich annotations, this covers what's needed: scope, soft-delete filtering, the lookup key, the fields returned (compensating for the absent output schema), and the sibling to use for a related resource.

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% and the property already explains that the GUID is the 'Id returned by IncidentList, MonitorIncidents, or HeartbeatIncidents.' The description repeats 'external GUID' but adds no format, casing, or lookup-failure semantics beyond the schema, so baseline 3 applies.

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

Purpose5/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 non-deleted incident summary'), the lookup key ('by external GUID'), the scope ('in the authenticated organization'), and the returned fields. 'One ... by external GUID' plus the 'incident summary' framing separates it from incident_list and incident_alert_history without needing the schema.

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?

Explicitly routes a neighboring need elsewhere: 'Use IncidentAlertHistory for delivery records.' It does not state the complementary case (use incident_list to find the GUID, or to enumerate incidents), though the schema parameter description fills that gap by naming IncidentList/MonitorIncidents/HeartbeatIncidents.

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

All PingRelay MCP Server tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?