Skip to main content
Glama
Sign In
swsd-mcp

swsd-mcp

by mikimatsub
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

swsd_update_incident_state

Destructive

Transition a SolarWinds Service Desk incident to a new state (Assigned, Resolved, Closed). Safer wrapper for updating state; check current state first.

Instructions

Transition an SWSD incident to a new state (e.g., "Assigned", "Resolved", "Closed"). Safer wrapper around swsd_update_incident — narrows the agent decision surface. State names are tenant-specific; common ones: "New - Unassigned", "Assigned", "In Progress", "Awaiting Input", "Resolved", "Closed". Call swsd_get_incident first to see the current state. WRITE — does not retry on transient failure.

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

Input Schema

NameRequiredDescriptionDefault
idYesSWSD incident reference. Accepts either the internal id (>=7 digits, e.g. 180457930) or the human-facing number (<=6 digits, e.g. 60310). The handler auto-detects via digit count.
stateYesNew state name. Must match a valid SWSD state for this tenant — common values: "New - Unassigned", "Assigned", "In Progress", "Awaiting Input", "Resolved", "Closed". Use swsd_get_incident to see the current state.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changedv2.3.1
    • addedInput schema / properties / state / maxLength
      Added value: +500
  3. First observedv2.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely new behavioral context — 'WRITE — does not retry on transient failure' and the fact that state names are tenant-specific — which the annotations cannot express. It stops short of saying whether an invalid or illegal transition errors out or silently no-ops.

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 core action and the wrapper rationale, and every sentence carries usable information. It loses a point for duplicating the common state-name list that already appears verbatim in the schema.

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 two-parameter mutation with no output schema, the description covers the prerequisite, the alternative tool, retry behavior, and tenant-specificity of state names. It does not address what a failed or rejected transition returns, which is the main remaining gap.

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 the schema already documents both id and state, including the auto-detection of id by digit count. The description largely repeats the schema's state-value list rather than adding new semantics, so the baseline 3 applies.

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 (transition an SWSD incident to a new state) and explicitly distinguishes itself from the sibling swsd_update_incident by calling itself a safer, narrower wrapper. An agent can select this over the general update tool without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit prerequisite (call swsd_get_incident first to see the current state) and names the alternative it is meant to replace (swsd_update_incident) with the reason to prefer it. The when-to-use condition is concrete rather than implied.

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

Deploy Server

Other Tools