Skip to main content
Glama
Sign In

Phare

by io.phare.mcp
OverviewDiscussionsAdmin

Delete an incident update

delete_incident_update
DestructiveIdempotent

Delete an incident update by ID, it disappears from the status pages and the state of the incident is recalculated, a recovered incident stays recovered. Only its author or a user with the incidents:moderate permission can delete it.

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": {
      "project_id": "<project_id>",
      "incident_id": "<incident_id>",
      "incident_update_id": "<incident_update_id>"
    },
    "name": "delete_incident_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesID of the project to act on, see whoami
incident_idYesID of the incident
incident_update_idYesID of the incident update to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond destructiveHint/idempotentHint annotations, it discloses concrete downstream effects: the update vanishes from status pages, the incident state is recalculated, and a recovered incident stays recovered. It also states the authorization model, which annotations do not cover at all.

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?

Two dense sentences, front-loaded with the action and side effects, with permissions last. The comma splices make it slightly run-on, but no sentence is filler.

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 destructive delete with no output schema, the definition covers side effects, state recalculation, and permissions — the things an agent needs before committing. It does not address failure modes (nonexistent update) or irreversibility explicitly, which annotations only imply.

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 all three IDs are already documented, including the pointer to whoami for project_id. The description only reinforces 'by ID' and adds no format or lookup guidance beyond the schema.

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 opens with a specific verb and resource ('Delete an incident update by ID'), which clearly separates it from delete_incident and update_incident_update in the sibling list. It stops short of explicitly naming those siblings, but the resource granularity is unambiguous.

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?

It supplies a real precondition for use: only the author or a holder of the `incidents:moderate` permission may delete. That is actionable selection guidance, though it gives no explicit when-not or alternative-routing advice (e.g. use update_incident_update instead of deleting).

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

All Phare toolsInspect
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