Skip to main content
Glama
mikimatsub

swsd-mcp

by mikimatsub
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

swsd_create_service_request

Submit a SolarWinds Service Desk catalog request to create an incident with form variable values; returns the new incident id for follow-up.

Instructions

Submit a SWSD catalog request, creating an incident with is_service_request: true (auto-set by SWSD on this endpoint) and the supplied form variable values. Use swsd_list_catalog_items to find the right catalog_item_id and swsd_get_catalog_item to inspect its variables before filling. Each request_variables entry needs custom_field_id (= the catalog item variable's id) and value (stringified to match the variable's kind — for dropdowns, one of the options choices). The created incident's id is returned for follow-up calls (swsd_get_incident, swsd_assign_incident, 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
descriptionNoOptional free-text description added to the resulting incident. The catalog item's default description from the SWSD UI is replaced if you pass this.
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.
catalog_item_idYesCatalog item id from `swsd_list_catalog_items` or `swsd_get_catalog_item`. The endpoint URL embeds this; SWSD auto-populates the resulting incident's name, category, and subcategory from the catalog item.
requester_emailNoEmail of the user the request is for. Defaults to the authenticated user (resolved from the JWT). SWSD rejects numeric requester ids on this endpoint, so pass an email if you need to file the request on behalf of someone else.
request_variablesNoForm variable values, one entry per catalog variable being filled. Use `swsd_get_catalog_item` first to discover the available variables and required ones (`required: "1"`).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
incidentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 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 / requester_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,}$"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed7 schema fields changedv2.3.1
    • 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 / description / maxLength
      Added value: +100000
    • addedInput schema / properties / request_variables / items / properties / value / maxLength
      Added value: +100000
    • addedInput schema / properties / request_variables / maxItems
      Added value: +100
    • addedInput schema / properties / requester_email / maxLength
      Added value: +320
  3. First observedv2.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing that calls do NOT retry on transient failure and prescribing verification via swsd_get_incident before retrying, plus a real API constraint (numeric requester ids are rejected, so an email is required to file on behalf of another user). This is exactly the non-obvious write-behavior context annotations cannot convey.

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?

Purpose and the write/retry warning are front-loaded, and every sentence carries operational content. It is a dense single paragraph with some parenthetical overlap against the schema, so slightly less scannable than ideal.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, yet the description still states what is returned (the created incident id) for chaining calls, and covers prerequisites, write semantics, failure handling, and per-type value formats. Nothing an agent needs to invoke this correctly is missing.

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 schema already documents all five parameters (baseline 3). The description adds some cross-referencing value by linking request_variables.custom_field_id to the catalog variable's id and stressing stringification by variable 'kind', though most of this duplicates the schema text.

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 ('Submit a SWSD catalog request, creating an incident with is_service_request: true'), which clearly distinguishes it from the sibling swsd_create_incident. The agent immediately understands the endpoint's effect without opening the 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: use swsd_list_catalog_items to find catalog_item_id, swsd_get_catalog_item to inspect variables, and swsd_describe_custom_fields before passing custom_fields. It also names the follow-up tools (swsd_get_incident, swsd_assign_incident) and states the condition for each.

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