Skip to main content
Glama
mikimatsub

swsd-mcp

by mikimatsub
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Hybrid

swsd_create_incident

Create a new SWSD incident with a required title and optional description, priority, requester, and custom fields, returning the incident ID for follow-up actions.

Instructions

Create a new SWSD incident. Required: name. Strongly recommended: description, requester_email, priority, category_name. The created incident's ID is returned for follow-up calls (swsd_assign_incident, swsd_add_incident_comment, etc.). WRITE — does not retry on transient failure; the agent should verify with swsd_get_incident before retrying. To set tenant-specific custom field values, pass custom_fields: [{name, value}] — call swsd_describe_custom_fields first to discover field names and (for Dropdowns) allowed values. Validated for Text, Dropdown, Number, Checkbox, and Date types.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesShort incident title (required).
priorityNoPriority name (e.g., "Low", "Medium", "High"). Tenant-specific values.
site_nameNoSite name (see swsd_list_sites).
descriptionNoLong-form description of the issue. Plain text or HTML.
category_nameNoCategory name (must match an existing SWSD category — see swsd_list_categories).
custom_fieldsNoSet tenant-specific custom field values on the record. Multi_picklist and User-type fields are not yet supported by this tool (set those via the SWSD UI). Validated for Text, Dropdown, Number, Checkbox, and Date types.
assignee_emailNoEmail of the agent to assign on creation. Use swsd_assign_incident later instead if you want to defer.
department_nameNoDepartment name (see swsd_list_departments).
requester_emailNoEmail of the user the ticket is for. Defaults to the token owner if omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv2.3.1
    • addedInput schema / properties / assignee_email / maxLength
      Added value: +320
    • addedInput schema / properties / category_name / maxLength
      Added value: +500
    • addedInput schema / properties / custom_fields / items / properties / name / maxLength
      Added value: +500
    • changedInput schema / properties / custom_fields / items / properties / value / anyOf
      Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  },
-  {
-    "type": "boolean"
-  }
-]New value: +[
+  {
+    "maxLength": 100000,
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  }
+]
    • addedInput schema / properties / custom_fields / maxItems
      Added value: +100
    • addedInput schema / properties / department_name / maxLength
      Added value: +500
    • addedInput schema / properties / description / maxLength
      Added value: +100000
    • addedInput schema / properties / priority / maxLength
      Added value: +500
    • addedInput schema / properties / requester_email / maxLength
      Added value: +320
    • addedInput schema / properties / site_name / maxLength
      Added value: +500
  2. First observedv2.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Discloses write behavior, non-retry on transient failures, and recommends verifying with get_incident before retrying. Also details custom field validation types, providing operational guidance beyond the annotations (which only indicate readOnly=false).

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?

The description is well-structured, front-loading the core action and then covering recommendations, error handling, and custom fields without redundancy. Each sentence adds value, and the length is appropriate for the complexity.

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?

Covers essential aspects: required/recommended fields, follow-up usage, error handling, and custom field discovery. For a tool with 9 parameters, it provides sufficient context, though it doesn't mention rate limits or output format beyond ID.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds meaning by marking required vs recommended parameters and explaining custom_fields usage and validation, going beyond raw schema definitions.

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: 'Create a new SWSD incident.' It clearly distinguishes from siblings like create_service_request by resource type, and mentions required and recommended fields, making its purpose unambiguous.

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?

Provides clear context for when to use (to create an incident), and instructs on handling custom fields (discover via describe_custom_fields). It does not explicitly contrast with alternative tools like create_service_request, but the resource type makes the usage clear.

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

Install Server

Other Tools