swsd-mcp

swsd_get_problem

Read-onlyIdempotent

Fetch one SolarWinds Service Desk ITIL problem record by internal ID or human-facing number; use long detail to include comments, audits, tasks, and time tracks.

Instructions

Fetch one SWSD problem (ITIL problem record) by id or number. Returns the full problem detail as returned by SWSD (passthrough). Use swsd_list_problems first if you only have a name or filter — IDs are not guessable. Pass detail_level: "long" to include comments, audits, tasks, and time_tracks in one call.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "swsd_get_problem"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	SWSD problem reference. Accepts either the internal id (>=7 digits) or the human-facing number (<=6 digits). The handler auto-detects via digit count.
`detail_level`	No	Use "long" for inline comments/audits/tasks/time_tracks. Default "short" is faster and cheaper.	short

Output Schema

Name	Required	Description	Default
`problem`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv3.0.0Oct 4, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

First observedv2.1.0May 28, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description adds real context beyond that: results are an unmodified SWSD passthrough, IDs are not guessable, and detail_level: "long" fans out into comments, audits, tasks and time_tracks in a single call. It stops short of noting rate limits, auth scope, or what happens on an unknown id.

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 short sentences, each doing distinct work — what it returns, how to find the id, and the optional expansion mode. No filler and the primary purpose is front-loaded.

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?

An output schema exists, so return-shape explanation is not required, and the description still usefully characterises the payload as a passthrough. Combined with the routing hint and detail_level guidance, an agent has everything needed to invoke it correctly; only error/not-found behavior is unaddressed.

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 coverage is 100%, and both the id digit-count rule and the enum meanings are already documented in the schema. The description's contribution ("IDs are not guessable", the long-mode contents list) largely restates that, so it sits at the baseline rather than adding new semantics.

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+resource ("Fetch one SWSD problem (ITIL problem record)") and the keying method (by id or number). It is immediately distinguishable from swsd_list_problems and the other list/get siblings in the toolset.

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_problems first if you only have a name or filter — IDs are not guessable." It also names the condition that selects the richer mode (detail_level: "long"), so both the tool-vs-sibling choice and the in-tool option choice are resolved.

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

Deploy Server