Skip to main content
Glama
mikimatsub

swsd-mcp

by mikimatsub

swsd_update_incident

Update an existing SWSD incident by providing its ID and the fields to change; only specified fields are modified.

Instructions

Update an existing SWSD incident. Pass id and any fields to change. Only fields you provide are sent — others stay as-is. For state transitions prefer swsd_update_incident_state (safer wrapper); for assignment prefer swsd_assign_incident; for comments use swsd_add_incident_comment. WRITE — does not retry on transient failure. 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
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.
nameNoNew short title.
descriptionNoNew description (replaces existing).
priorityNoNew priority name.
category_nameNoNew category name.
site_nameNoNew site name.
department_nameNoNew department name.
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.
Behavior4/5

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

Beyond annotations (readOnlyHint=false), the description adds that it is a WRITE operation without retry on transient failure, and only specified fields are sent. This is transparent but could detail failure handling.

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 concise (5 sentences) with no wasted words, front-loaded with the main action, and uses clear structure with bullet-like points for alternatives.

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?

Given no output schema, the description covers key behavioral traits, alternatives, and custom field integration. It lacks error handling details but is complete for typical use.

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?

With 100% schema coverage, the description adds extra value for 'id' (auto-detection of format) and 'custom_fields' (validation, unsupported types, prerequisite tool call). Other parameters rely on schema descriptions.

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?

The description explicitly states the verb 'Update' and the resource 'SWSD incident', and distinguishes from siblings by suggesting alternatives like swsd_update_incident_state and swsd_assign_incident for specific actions.

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?

Provides clear usage guidance: when to use alternatives for state transitions, assignments, and comments; how to handle custom fields with a prerequisite call; and notes that only provided fields are changed.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mikimatsub/swsd-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server