swsd-mcp

swsd_list_catalog_items

Read-onlyIdempotent

List service request templates from SolarWinds Service Desk to find available offerings. Filter by site, department, state, or search text to identify the right catalog item for a request.

Instructions

List catalog items available in SolarWinds Service Desk. Each item represents an offerable service request template (e.g., "New Employee Onboarding", "Software Request") with a defined set of input variables (form fields). Use swsd_get_catalog_item to inspect a single item's variables, then swsd_create_service_request to submit a request.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	Page number (1-indexed).
`site`	No	Filter by site name.
`query`	No	Free-text search across catalog item names + descriptions (maps to the SWSD `name` query param).
`state`	No	Filter by state ("Approved", "Internal", or "Draft").
`per_page`	No	Results per page (1-100). SWSD caps at 100.
`department`	No	Filter by department name.

Output Schema

TableJSON Schema

Name	Required	Description
`items`	Yes
`pagination`	Yes
`applied_filters`	Yes	Echo of the filters applied to this query — empty object if none. Use this to reason about whether the result count reflects your filters or the tenant total.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv2.3.1Aug 22, 2026
- addedInput schema / properties / department / maxLength
```
Added value: +500
```
- addedInput schema / properties / query / maxLength
```
Added value: +2000
```
- addedInput schema / properties / site / maxLength
```
Added value: +500
```
- addedInput schema / properties / state / maxLength
```
Added value: +500
```
First observedv2.1.0May 28, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds domain context about catalog items but does not disclose much additional behavioral detail, such as pagination behavior or visibility rules; however, with strong annotations, this gap is acceptable.

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, all purposeful: the first states the core action, the second gives essential domain context, and the third routes the agent to the correct next steps. There is no filler or 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?

For a read-only listing tool, the description, combined with 100% schema coverage, rich annotations, and an existing output schema, is complete. It tells the agent what the items represent, how to inspect one, and how to submit a request afterward.

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 every parameter, including page, site, query, state, per_page, and department, is already documented in the schema. The description adds no parameter-level meaning beyond what the schema provides, so the 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 opens with a specific verb and resource: 'List catalog items available in SolarWinds Service Desk.' It also adds semantic context by defining items as offerable service request templates with input variables, and it distinguishes itself from the sibling swsd_get_catalog_item, which inspects a single item's variables.

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 names the workflow: use swsd_get_catalog_item to inspect variables, then swsd_create_service_request to submit. This tells an agent not only what this tool does but where it fits among its siblings, providing clear selection guidance.

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

Install Server