Skip to main content
Glama

Post a status page update

post_incident_update

Publishes an update on every published status page that shows the incident's monitor and in their RSS and Atom feeds, and on Pro plans emails those pages' subscribers. States: investigating, identified, monitoring, resolved. Write for the page's visitors. Free.

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": {
      "incident_id": "<incident_id>",
      "state": "<state>",
      "message": "<message>"
    },
    "name": "post_incident_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYesWhere the work on the incident stands; the pages show it with the update.
titleNoOptional title on the pages, such as "Slow checkout".
messageYesThe update's text, as the pages' visitors read it.
incident_idYesIncident ID from list_incidents.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / message / description
      Added value: +"The update's text, as the pages' visitors read it."
    • addedInput schema / properties / state / description
      Added value: +"Where the work on the incident stands; the pages show it with the update."
  2. First observed

TDQS

A3.9/5.0
Behavior5/5

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

The annotations only say this is a non-idempotent, open-world write; the description supplies the critical consequences the agent needs: the update is public on every published status page tracking that monitor, syndicates to RSS and Atom, and emails subscribers on Pro plans. That side-effect disclosure (external visibility plus outbound email) goes well beyond what the structured annotations convey.

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 effect of the call, then constraints, then audience guidance — no filler. The trailing fragments "Write for the page's visitors. Free." are terse to the point of being slightly cryptic, but they cost almost no length.

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 public-facing write tool with no output schema, the definition covers the essential questions: what becomes visible, where it goes, and what values state accepts. It stops short of lifecycle details (can a posted update be edited or removed, are there rate limits or plan restrictions beyond the Pro emailing note), which keeps it from being fully complete.

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 state, message, title, and incident_id are already fully documented in the schema. The description largely restates the state enum values and adds only audience framing ("Write for the page's visitors"), which is useful but minimal against a schema that already carries the load.

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 states a specific verb and resource ("Publishes an update") and precisely scopes the blast radius: every published status page showing the incident's monitor, plus RSS/Atom feeds and subscriber emails on Pro. That public-publishing scope implicitly separates it from internal actions like comment_on_incident or update_incident, though no sibling is named to make the distinction explicit.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the four permitted states (investigating, identified, monitoring, resolved) and "Write for the page's visitors" tell the agent what kind of content belongs here, but there is no explicit when-to-use versus comment_on_incident/update_incident, and no prerequisites such as required permissions or whether an incident must be open.

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