Skip to main content
Glama
mikimatsub

swsd-mcp

by mikimatsub

swsd_list_problems

Read-onlyIdempotent

List and filter SWSD problem records to identify root causes of recurring incidents, with pagination and compact summaries.

Instructions

List SWSD problems (ITIL problem records) with structured filters and pagination. Returns compact summaries (id, name, state, priority, category, requester, assignee, updated_at) — call swsd_get_problem for the full detail of any one row. Filters use SWSD repeated-key array semantics (multiple values within a filter are OR-ed). Use this when investigating recurring incidents or identifying root causes that span multiple tickets.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stateNoFilter to problems matching ANY of these states (e.g. ["New", "In Progress"]).
state_is_notNoNegative state filter: exclude problems in any of these states (e.g. ["Resolved", "Closed"]).
priorityNoFilter to problems matching ANY of these priorities (e.g. ["High", "Medium"]).
assignee_emailNoFilter to problems assigned to this email.
requester_emailNoFilter to problems requested by this email.
queryNoFree-text search on name + description.
per_pageNoResults per page (1-100). SWSD caps at 100.
pageNoPage number (1-indexed).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
problemsYes
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 readOnlyHint, idempotentHint, openWorldHint: true. The description adds value beyond annotations by clarifying the compact summary return format and the OR-ed filter semantics. It does not contradict 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?

Two sentences, front-loaded with purpose and key details. No unnecessary words. Every sentence earns its place.

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 complexity (8 parameters, output schema exists), the description is complete. It explains the compact return format, filter semantics, and typical use case. The output schema handles return details, so no need for further elaboration.

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 each parameter having a description. The description adds meaning beyond the schema by explaining that filters use SWSD repeated-key array semantics (OR-ed within a filter). Baseline 3, elevated due to extra context.

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?

Description clearly states it lists SWSD problems with structured filters and pagination, specifies returned fields (id, name, state, etc.), and distinguishes from swsd_get_problem (full detail). Also explains use case: investigating recurring incidents or root causes. This is a specific verb+resource with clear scope and differentiation from siblings.

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?

Description explicitly says 'Use this when investigating recurring incidents or identifying root causes that span multiple tickets,' providing clear context for when to use. It also notes that filters use OR-ed semantics. However, it does not explicitly contrast with other list tools like swsd_list_incidents or state when not to use this tool.

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