Skip to main content
Glama
mikimatsub

swsd-mcp

by mikimatsub
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

swsd_list_catalog_items

Read-onlyIdempotent

List and search SolarWinds Service Desk catalog items to find offerable service request templates, such as onboarding or software requests, before inspecting their fields and submitting 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
NameRequiredDescriptionDefault
pageNoPage number (1-indexed).
siteNoFilter by site name.
queryNoFree-text search across catalog item names + descriptions (maps to the SWSD `name` query param).
stateNoFilter by state ("Approved", "Internal", or "Draft").
per_pageNoResults per page (1-100). SWSD caps at 100.
departmentNoFilter by department name.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYes
paginationYes
applied_filtersYesEcho 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.

  1. Changed2 schema fields changedv3.0.0
    • 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"
  2. Changed4 schema fields changedv2.3.1
    • 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
  3. First observedv2.1.0

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds useful context about what a catalog item is and how it fits the workflow, but does not disclose pagination behavior, rate limits, or return shape. Given annotations carry the safety burden, a 3 is appropriate.

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, front-loaded with the primary action, then a clarifying definition, then routing guidance. Every sentence earns its place with no filler.

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 list tool with an output schema present, annotations covering safety, and 100% schema description coverage, the description is complete. It defines the resource, its role in the workflow, and the sibling tools to chain with. Return values are covered by the output schema.

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% with all six parameters documented inline (including the SWSD name mapping note for query). The description adds no parameter-level detail beyond what the schema already provides, so the baseline of 3 applies.

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 ('List catalog items available in SolarWinds Service Desk') and clarifies what an item represents (offerable service request template with input variables). It is clearly distinguishable from sibling tools like swsd_get_catalog_item and swsd_create_service_request.

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_get_catalog_item to inspect a single item's variables, then swsd_create_service_request to submit a request. This names the alternatives and the conditions for each, leaving nothing to inference.

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

Deploy Server

Other Tools