Skip to main content
Glama
mikimatsub

swsd-mcp

by mikimatsub

swsd_list_catalog_items

Read-onlyIdempotent

Retrieve a paginated list of service request templates from SolarWinds Service Desk, with filters for state, department, site, and name search.

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).
per_pageNoResults per page (1-100). SWSD caps at 100.
stateNoFilter by state ("Approved", "Internal", or "Draft").
departmentNoFilter by department name.
siteNoFilter by site name.
queryNoFree-text search across catalog item names + descriptions (maps to the SWSD `name` query param).

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.
Behavior4/5

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

Annotations already declare read-only, idempotent, and open-world hints. Description adds context about catalog items' nature and relation to other operations, strengthening behavioral understanding beyond annotations.

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: purpose, definition, workflow. Every sentence serves a purpose, front-loaded, no superfluous content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With output schema present, description need not detail returns. Covers tool purpose and integration with sibling tools. Lacks explicit mention of pagination behavior, but schema parameters hint at it.

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 coverage is 100% with detailed descriptions. Description adds value by explaining the broader purpose of catalog items, helping interpret filters, but does not add specific parameter info beyond schema.

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 clearly states the tool lists catalog items, specifies what catalog items are (service request templates), and names sibling tools for further actions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit workflow guidance: list items, then use swsd_get_catalog_item for details, then swsd_create_service_request to submit. Does not explicitly mention when to avoid this tool, but context is sufficient.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mikimatsub/swsd-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server