Skip to main content
Glama

vspc_resolve_alarm

Marks a triggered VSPC alarm as resolved with a comment explaining the fix. Use it to clear alarms after remediation; if the cause remains, VSPC triggers the alarm again.

Instructions

Marks a triggered VSPC alarm as resolved, with a comment. If the cause is still there, VSPC triggers it again.

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": {
      "alarm_uid": "<alarm_uid>",
      "comment": "<comment>"
    },
    "name": "vspc_resolve_alarm"
  }
}

Input Schema

NameRequiredDescriptionDefault
commentYesHow it was resolved (shown in VSPC; up to 512 characters).
alarm_uidYesTriggered alarm UID (instanceUid from vspc_list_alarms).
on_client_portalNoAlso resolve it on the client's portal.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare a non-read-only, non-destructive, non-idempotent, open-world mutation, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the resolution is not a permanent suppression, because VSPC re-triggers the alarm if the underlying cause persists. It does not mention permission requirements or what the response contains.

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?

Two tight sentences, front-loaded with the action and followed by the one caveat that matters. No filler; the only loss is that the caveat could be framed as a usage consequence rather than a trailing note.

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?

A simple three-parameter mutation with a fully described schema and no output schema; the description covers the action and the key re-trigger caveat. The remaining gap is the absence of any distinction from vspc_acknowledge_alarm, which matters for correct tool selection.

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 all three parameters (alarm_uid, comment, on_client_portal) are fully documented in the schema itself. The description only echoes the comment requirement and adds nothing about the client-portal flag or the alarm_uid source, so 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?

States a specific verb and resource: marks a triggered VSPC alarm as resolved, with a comment. This is clearly actionable and distinct from read-only siblings like vspc_list_alarms, though it does not explicitly differentiate itself from vspc_acknowledge_alarm.

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 by 'triggered alarm' and the requirement of a resolution comment, but there is no explicit when-to-use guidance and no mention of when to prefer vspc_acknowledge_alarm over resolving. The agent must infer the choice from the sibling name alone.

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