Skip to main content
Glama
Sign In

Visual Sentinel

by com.visualsentinel
OverviewDiscussionsAdmin

Mark an incident resolved

vs_incidents_mark_resolved
DestructiveIdempotent

Mark an incident resolved now and leave the site's settings as they are. It opens again if the problem comes back. The incident's alert channels and status page subscribers are told it is resolved unless notify is false.

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

Input Schema

NameRequiredDescriptionDefault
idYesIncident id.
notifyNofalse records the change without telling the incident's alert channels and status page subscribers (default true).
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

A4/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, but the description adds genuinely new behavior: the incident reopens automatically if the problem recurs, and alert channels plus status page subscribers are notified unless notify is false. The only gap is what the response contains, which is minor given no output schema.

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 short sentences, front-loaded with the action and scope, then the auto-reopen consequence, then the notification rule. Nothing repeats the schema or wastes space.

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 one-required-param mutation with full schema coverage and no output schema, the description covers the side effects an agent most needs: notifications, suppression via notify, and automatic reopening. Return payload expectations are the one thing left unaddressed.

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 id, notify and actionId are fully documented in the schema itself. The description reinforces the notify semantics (who gets told, and the false case) but adds no format or syntax detail beyond that, so the baseline 3 applies.

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?

"Mark an incident resolved now and leave the site's settings as they are" gives a specific verb plus resource and adds a scope qualifier (no settings changes) that separates it from the options-based sibling. It never names vs_incidents_resolve_options or vs_alerts_resolve explicitly, so the differentiation is implied rather than stated.

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?

The description gives clear context for choosing this tool: immediate resolution, settings untouched, and auto-reopen on recurrence, all of which contrast with vs_incidents_resolve_options. It stops short of naming an alternative or stating when not to use it.

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