swsd-mcp

swsd_get_solution

Read-onlyIdempotent

Fetch a SolarWinds Service Desk solution by numeric ID to retrieve its full HTML and plain-text description, custom fields, comment count, and attachments.

Instructions

Fetch one SWSD solution by numeric ID. Returns the full solution as returned by SWSD (passthrough), including both description (HTML) and description_no_html (plain text) fields, custom_fields_values, comments count, and attachment metadata. Use swsd_search_solutions first if you only have a topic — IDs are not guessable. Pass detail_level: "long" to include attachments, audits, and tags in one call.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	SWSD solution reference. Accepts either the internal id (>=7 digits) or the human-facing number (<=4 digits). The handler auto-detects via digit count.
`detail_level`	No	Use "long" to include attachments, audits, tags, and full statistics in one call. Default "short" is faster.	short

Output Schema

TableJSON Schema

Name	Required	Description	Default
`solution`	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.5/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 genuinely new behavioral context: the response is a raw SWSD passthrough with dual HTML/plain-text description fields, IDs are unguessable, and "long" detail pulls attachments, audits and tags in a single call. It stops short of noting pagination or error behavior, but for a single-record read the gaps are minor.

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, each load-bearing: identity/scope, return shape, and the two behavioral caveats (search first, long detail). The routing advice is front-loaded where an agent will act on it.

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?

Output schema exists and annotations cover the safety profile, so the description only needs to cover usage routing and the detail_level tradeoff, which it does. Nothing an agent needs to invoke this 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 documents the id auto-detection (>=7 digit internal id vs <=4 digit human number) and the detail_level enum with its default. The description's detail_level note largely restates the schema, adding no new syntax, format, or edge-case guidance. Baseline 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?

States a specific verb and resource ('Fetch one SWSD solution by numeric ID') and immediately enumerates what the returned object contains (description HTML, description_no_html, custom_fields_values, comment count, attachment metadata). An agent can distinguish this from swsd_search_solutions without opening either schema.

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_search_solutions first if you only have a topic — IDs are not guessable.' It also states the condition for escalating to detail_level: "long" (attachments/audits/tags in one call), giving both when-to-use and an alternative.

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

Deploy Server