Skip to main content
Glama
mikimatsub

swsd-mcp

by mikimatsub

swsd_create_problem

Create an ITIL problem record to document root-cause analysis and known-error tracking for recurring incidents. Requires a problem title.

Instructions

Create a new SWSD problem (ITIL problem record). Required: name. Strongly recommended: description, priority, category. The created problem's id is returned for follow-up calls. Use this when promoting a recurring incident to a problem record so root-cause analysis and known-error tracking can be tied to multiple incidents. WRITE — does not retry on transient failure; the agent should verify with swsd_get_problem before retrying.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesProblem title (required).
descriptionNoDescription (HTML or plain text).
priorityNoPriority name (e.g. High, Medium, Low). Tenant-specific values.
categoryNoCategory name (must match an existing SWSD category — see swsd_list_categories).
subcategoryNoSubcategory name (nested under category).
assignee_emailNoEmail of the agent to assign the problem to.
requester_emailNoEmail of the user the problem is for. Defaults to the token owner if omitted.
Behavior4/5

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

Discloses that it is a write operation, not idempotent, and does not retry on transient failure. Adds value over annotations by detailing retry behavior and that the created problem's id is returned.

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?

Two sentences: first covers purpose and parameters, second covers usage and retry. Front-loaded, no redundancy.

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?

Given 7 parameters, no output schema, and no nested objects, the description sufficiently covers output (id returned), retry behavior, and parameter recommendations, making it complete for agent invocation.

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%, but description adds prioritization of parameters (required vs strongly recommended), which aids parameter selection beyond 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 clearly states the action (Create) and resource (SWSD problem) and differentiates from siblings by specifying the use case of promoting a recurring incident to a problem record.

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 states required and recommended parameters, provides a clear usage scenario (promoting recurring incident), and gives retry guidance (verify with swsd_get_problem).

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