Skip to main content
Glama
mikimatsub

swsd-mcp

by mikimatsub
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

swsd_assign_incident

Destructive

Assign a SolarWinds Service Desk incident to an agent by email. Use it to route a ticket to a valid assignee without updating other incident details.

Instructions

Assign an SWSD incident to an agent by email. Safer wrapper around swsd_update_incident — narrows the agent decision surface to "who gets this ticket." Use swsd_list_users with available_for_assignment_only=true to find valid assignees first. WRITE — does not retry on transient failure.

Input Schema

TableJSON 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.
assignee_emailYesEmail of the agent to assign. Must be an SWSD user with available_for_assignment=true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields 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"
    • changedInput schema / properties / assignee_email / pattern
      Previous value: -"^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"New value: +"^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
  2. Changed1 schema field changedv2.3.1
    • addedInput schema / properties / assignee_email / maxLength
      Added value: +320
  3. First observedv2.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare the write/destructive/open-world profile, so the bar is lower, and the description adds a trait the annotations do not: 'WRITE — does not retry on transient failure,' which tells the agent a failure is terminal and retrying is its own responsibility. It doesn't cover auth requirements or a response shape, but the added operational context is meaningful.

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, all front-loaded: purpose first, then sibling relationship, then prerequisite, then the write caveat. No filler and every clause carries distinct information.

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 write semantics, the failure behavior, and the assignee-discovery prerequisite. It does not describe what a successful assignment returns or what happens if the email is not an assignable user, leaving a small 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 both id and assignee_email are already fully documented, including the id format auto-detection and the assignee_email validity constraint. The description's only added semantics is the pointer to swsd_list_users for finding valid assignees, which is usage guidance rather than new parameter meaning. 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 ('Assign an SWSD incident to an agent by email') and immediately positions itself against the sibling swsd_update_incident by explaining it is a narrower alternative. An agent can distinguish it from swsd_update_incident 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?

Explicitly routes the agent: it names the alternative (swsd_update_incident) it wraps, tells the agent to use swsd_list_users with available_for_assignment_only=true to find valid assignees first, and states the decision surface is deliberately narrowed to 'who gets this ticket.' This is when-to-use plus a prerequisite workflow.

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