Pingstack

Post incident update

create_incident_update

Post a status update on an incident, as the person who approved this connection. The text appears in the incident's timeline in the app and, when the incident's check is on a public dashboard that shows incident history, on that status page right away. Updates can't be edited or deleted here, and each call adds a new one. Doesn't open, resolve or change the incident. Returns the update's id, text, author and time.

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>",
      "body": "<body>"
    },
    "name": "create_incident_update"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Incident id, the numeric id an incident listing reports.
`body`	Yes	The update's text, up to 10,000 characters. Shown as written on public status pages that include this incident.

Output Schema

Name	Required	Description	Default
`id`	Yes
`body`	Yes
`created_at`	Yes
`author_name`	Yes
`incident_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 10, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Goes well past the annotations: it discloses the immediate external side effect (text appears in the timeline and on any public dashboard showing incident history), that updates are immutable and non-idempotent (consistent with idempotentHint=false, destructiveHint=false), and that the incident state itself is untouched.

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?

Front-loaded with the action, then scope boundary, then durability rules and return fields; no filler sentences. The return-value sentence duplicates the existing output schema, which is the only wasted line.

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 two-parameter append operation the description covers side effects, immutability, author attribution, and the fact the incident is not modified, with return shape available in the output schema. An agent has everything needed to call it correctly.

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% and both parameters are already documented with lengths and a pattern, so the baseline applies. The description only restates that the body text is displayed as written on public pages, adding marginal meaning beyond the schema.

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 ('Post a status update on an incident') and immediately bounds it with 'Doesn't open, resolve or change the incident', which separates it from get_incident/list_incidents and the check-mutating siblings.

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?

Gives clear context for use: it posts as the approving user, it is append-only ('each call adds a new one'), and it cannot edit or delete, which implicitly tells the agent not to look for an edit path here. It stops short of naming an explicit alternative, so it is not a full 5.

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

All Pingstack tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?