Skip to main content
Glama
Sign In
OpenUptime

OpenUptime

by becoolme
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

acknowledge_incident

Assign an existing incident to yourself to take ownership of an investigation. Returns the incident record; it does not resolve the incident or notify subscribers.

Instructions

Assign an existing incident to the authenticated caller and return the incident record. Use this when taking ownership of an investigation; it does not resolve the incident or post a subscriber update. Use post_incident_update to communicate status, and list_incidents to discover the incident UUID.

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": {
      "id": "<id>"
    },
    "name": "acknowledge_incident"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesResource UUID returned by the matching list tool; not its name, incident number or status-page slug.
projectNoProject id (from list_workspaces). Omit to use the default project of the workspace.
workspaceNoWorkspace id (from list_workspaces). Omit to use the default one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.1
    • changedInput schema / properties / id / description
      Previous value: -"Resource id (uuid)"New value: +"Resource UUID returned by the matching list tool; not its name, incident number or status-page slug."
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

The description adds meaningful behavior beyond the annotations: it assigns the incident to the authenticated caller, returns the incident record, does not resolve the incident, and does not post a subscriber update. It does not mention permission requirements, reassignment behavior, or what happens on repeated acknowledgement, so it stops short of fully rich behavioral disclosure.

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?

The description is three focused sentences with the core action front-loaded. Every sentence earns its place by covering purpose, usage boundaries, and alternatives without redundancy.

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 simple mutation tool with annotations covering safety traits, the description is complete enough to call correctly: it explains the assignment action, the non-effects, the expected return, and how to obtain the required incident UUID. No output schema exists, but the description sufficiently indicates that an incident record is returned.

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%, so the input schema already documents all three parameters, including the UUID format and the warning not to use an incident name, number, or slug. The description names list_incidents as the source of the incident UUID, which is useful, but it does not add syntax or format details beyond the schema and says nothing extra about the optional project and workspace parameters.

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?

The description states a specific verb and resource: "Assign an existing incident to the authenticated caller and return the incident record." It also distinguishes this action from resolving the incident or posting a subscriber update, making it clearly different from sibling tools such as update_incident and post_incident_update.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit when-to-use guidance: "Use this when taking ownership of an investigation." It also states what the tool does not do and names the correct alternatives for communicating status (post_incident_update) and discovering the incident UUID (list_incidents).

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