Skip to main content
Glama
mikimatsub

swsd-mcp

by mikimatsub
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Hybrid

swsd_assign_incident

Destructive

Assign an SWSD incident to an agent using their email, narrowing assignment decisions to the specific agent. Find valid assignees first via list_users, then update the ticket.

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. Changed1 schema field changedv2.3.1
    • addedInput schema / properties / assignee_email / maxLength
      Added value: +320
  2. First observedv2.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already mark this as a non-read-only, non-idempotent, destructive write. The description adds value beyond that by explicitly stating 'WRITE — does not retry on transient failure,' which is a critical behavioral trait not present in the annotations. It also explains the safety-wrapper rationale.

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 sentences with no filler: the action is front-loaded, the wrapper context is concise, and the prerequisite lookup is stated in one clear instruction. Every sentence earns its place.

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?

For a simple two-parameter write tool with complete schema coverage and annotations, the description covers the essential operational context: what it does, how it relates to siblings, how to find valid assignees, and the retry behavior. Nothing needed to call it correctly is missing.

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 fully documents both parameters, including the id auto-detection rule and the assignee availability requirement. The description adds no new parameter-level detail beyond what the schema provides, so the baseline of 3 is appropriate.

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 opens with a specific verb and resource: 'Assign an SWSD incident to an agent by email.' It also distinguishes itself from the broader swsd_update_incident by framing this as a narrower wrapper, so an agent can immediately tell what this tool is for.

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?

The description explicitly instructs the agent to use swsd_list_users with available_for_assignment_only=true to find valid assignees first, and frames the tool as a safer alternative to swsd_update_incident. This gives clear when-to-use and how-to-prepare guidance.

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