swsd-mcp

swsd_get_solution

Read-onlyIdempotent

Fetch a SWSD solution by numeric ID, including HTML and plain-text descriptions, custom fields, comments count, and attachment metadata. Set detail_level 'long' for audits, tags, 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.

First observedv2.1.0May 28, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is clear. The description adds valuable context beyond annotations: it discloses passthrough behavior (raw SWSD response), lists key fields returned, and explains the ID auto-detection nuance. The note 'IDs are not guessable' further clarifies why a search-first workflow is necessary.

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 carrying essential information: what the tool does, what it returns, and usage guidance for parameters. The most important fact (fetch by ID) is front-loaded, and no words are wasted. It is compact yet comprehensive.

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 the 2-parameter schema with rich descriptions, a full output schema, and safety annotations, the description covers all essential aspects: purpose, prerequisites (search first), return content, and optional detail_level. Nothing critical for invoking the tool correctly is missing.

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 description coverage is 100%, so the baseline is 3. The description adds meaningful extra guidance by explaining that IDs are not guessable and recommending swsd_search_solutions as the source for the id parameter. However, it largely echoes the schema's detail_level description, so the added value is modest beyond the non-guessability hint.

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: 'Fetch one SWSD solution by numeric ID.' It clearly distinguishes this from sibling tools like swsd_get_incident and swsd_search_solutions by focusing on 'solution' as the resource. It also specifies the exact return shape, which removes ambiguity about what the tool does.

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 to use swsd_search_solutions first if the user only has a topic, stating that IDs are not guessable. It also provides clear guidance on when to pass detail_level: 'long' to include attachments, audits, and tags. This leaves no doubt about when to choose this tool or how to adjust its behavior.

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

Install Server