Skip to main content
Glama
Sign In

Visual Sentinel

by com.visualsentinel
OverviewDiscussionsAdmin

Post an incident update

vs_incidents_post_update
Destructive

Post a timeline update to an incident (shown on status pages) and set its status. It is sent to the incident's alert channels and status page subscribers unless notify is false. Needs an owner or admin account.

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>",
      "status": "<status>",
      "message": "<message>"
    },
    "name": "vs_incidents_post_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesIncident id.
notifyNofalse records the change without telling the incident's alert channels and status page subscribers (default true).
statusYesINVESTIGATING, IDENTIFIED, MONITORING, RESOLVED or POSTMORTEM.
messageYesThe update text (up to 2000 characters).
actionIdNoOptional UUID you make once per action, so a retried call is not applied or announced twice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already flag destructive/non-idempotent/openWorld, and the description adds genuinely new context: the update appears on status pages, is broadcast to alert channels and subscribers, and can be silenced with notify=false, plus the owner/admin auth requirement. It stops short of noting that retries are deduped via actionId despite idempotentHint=false, which would have closed the loop.

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?

Three sentences, each carrying new information, with the core action and its visibility front-loaded and the notification/auth caveats following. No 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?

There is no output schema, and the description covers effect, audience, auth, and the silent-mode option, which is enough for an agent to call it safely. Minor gaps remain on retry/dedup behavior and what the call returns.

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 each parameter is documented, so the baseline applies. The description restates notify's effect and the status-setting behavior but adds no syntax, format, or default detail 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?

States a specific verb and resource: posting a timeline update to an incident and setting its status, with the visible effect (status pages) called out. It would be stronger if it explicitly distinguished itself from the sibling vs_incidents_update and vs_incidents_mark_resolved, which sound adjacent.

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?

It gives the prerequisite (owner or admin account) and the side effect (notifications), so usage context is implied. But there is no explicit when-to-use guidance versus vs_incidents_update, vs_incidents_mark_resolved, or vs_incidents_resolve_options, and no when-not-to-use note.

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

All Visual Sentinel toolsInspect
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