Skip to main content
Glama

Publish a drafted incident post

publish_incident_post
DestructiveIdempotent

Use this when the user has approved a draft_incident_post draft's exact text and recipients. Posts it as the dashboard's Incidents tab does: it shows on the status pages and FlareWarden emails the subscribers, members and webhooks the draft named. Returns the incident. Safe to repeat: the same draft id posts once and returns the first result. Not for changing the text: make a new draft.

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": {
      "draft_id": "<draft_id>",
      "confirm": "<confirm>"
    },
    "name": "publish_incident_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesThe plan's confirm sentence, exactly as returned; show it to the user first.
draft_idYesThe draft's id from draft_incident_post (it starts with pl_).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Goes beyond annotations by naming the actual side effects (status page publication, emails to subscribers/members/webhooks recorded on the draft) and the idempotency semantics ('same draft id posts once and returns the first result'), which annotations only flag abstractly as openWorld/destructive/idempotent. Missing only failure behavior or required permissions.

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?

Four short sentences, front-loaded with the triggering condition, then effects, then idempotency, then the exclusion. No filler.

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 2-parameter destructive publish with a full schema and no output schema, it covers precondition, blast radius, idempotency, and return value ('Returns the incident'). Nothing an agent needs to call it correctly is absent.

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 both draft_id (pl_ prefix, from draft_incident_post) and confirm (plan's confirm sentence) are already fully documented in the schema. The description adds no parameter-level detail, so the 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 action (publish a drafted incident post) and characterizes it precisely against the dashboard's Incidents tab. Explicitly distinguishes itself from draft_incident_post with 'Not for changing the text: make a new draft.'

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?

Gives an explicit precondition ('when the user has approved a draft_incident_post draft's exact text and recipients') and an explicit exclusion routing agents to draft_incident_post for text changes. Both the when and the when-not are present.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources