swsd-mcp

swsd_get_incident

Read-onlyIdempotent

Retrieve a SolarWinds Service Desk incident by its numeric ID. Use short detail for speed or long detail to get comments, attachments, audits, and resolution in one call.

Instructions

Fetch one SWSD incident by numeric ID. Returns the full incident detail as returned by SWSD (passthrough), including custom_fields_values when present. Use swsd_list_incidents first if you only have a name or filter — IDs are not guessable. Pass detail_level: "long" to include comments, attachments, audits, SLA data, and resolution in one call.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	SWSD 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.
`detail_level`	No	Use "long" to include comments, attachments, audits, SLA data, tags, statistics, satisfaction, and resolution detail in one call. Default "short" is faster and cheaper. Recommend "long" when the user asks "show me everything about ticket X" or wants comments/attachments/audits.	short

Output Schema

TableJSON Schema

Name	Required	Description	Default
`incident`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.0May 28, 2026

TDQS

A4.5/5.0

Behavior4/5

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

The description goes beyond annotations by disclosing that the result is a passthrough from SWSD, includes custom_fields_values when present, and that 'long' adds comments, attachments, audits, SLA data, and resolution. This helps the agent anticipate the response shape and breadth without contradicting the read-only, idempotent, non-destructive hints.

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 tight sentences deliver purpose, return behavior, workflow routing, and parameter guidance with no filler. The most important facts are front-loaded, and 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?

The output schema handles return structure, the annotations handle safety/idempotency, and the description covers lookup strategy, ID constraints, and detail-level tradeoffs. For a read-only fetch-by-ID tool, there is no material gap preventing correct invocation.

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?

The schema already documents both parameters fully with 100% coverage, including the ID format/auto-detection rule and the detail_level behavior. The description adds little parameter-level meaning beyond reinforcing those points, so a baseline score 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 states a specific verb ('fetch'), resource ('one SWSD incident'), and selection criterion ('by numeric ID'). It also distinguishes itself from the sibling list tool by noting that swsd_list_incidents should be used when only a name or filter is available, making the purpose unambiguous.

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?

It explicitly routes the agent to swsd_list_incidents when it lacks an ID, and explains why IDs are not guessable. It also gives clear guidance on when to use detail_level 'long' (include comments, attachments, audits, SLA data, and resolution), so the agent can decide correctly at call time.

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

Install Server