Skip to main content
Glama
mikimatsub

swsd-mcp

by mikimatsub

swsd_list_incidents

Read-onlyIdempotent

List SWSD incidents filtered by state, priority, category, dates, assignee, requester, site, department, group, or free-text query. Returns compact summaries with pagination.

Instructions

List SWSD incidents with structured filters and pagination. Returns compact summaries (id, name, state, priority, assignee_email, requester_email, category, updated_at) — call swsd_get_incident for the full detail of any one row. Filters use SWSD repeated-key array semantics (multiple values within a filter are OR-ed). NOTE: assignee_email and requester_email are applied CLIENT-SIDE because SWSD /incidents.json silently ignores them server-side (verified 2026-05-08 against the live API). Other filters (state, category, dates, sites, departments, assigned_to_group, query) DO narrow server-side and are passed through.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (1-indexed).
per_pageNoResults per page (1-100). SWSD caps at 100.
statesNoFilter to incidents matching ANY of these states (e.g. ["New", "Assigned"]).
prioritiesNoFilter to incidents matching ANY of these priorities (e.g. ["High", "Medium"]).
categoriesNoFilter to incidents matching ANY of these category names.
assignee_emailNoFilter to incidents assigned to this email.
requester_emailNoFilter to incidents requested by this email.
updated_fromNoFilter to incidents updated on or after this ISO date or datetime (YYYY-MM-DD or RFC 3339).
updated_withinNoConvenience alias for updated_from. Accepts "Nh" (hours), "Nd" (days), or "Nw" (weeks). Examples: "24h", "7d", "1w", "30d". Ignored if updated_from is explicitly set.
updated_toNoFilter to incidents updated on or before this ISO date or datetime. Pair with updated_from for an explicit range.
created_fromNoFilter to incidents created on or after this ISO date or datetime (YYYY-MM-DD or RFC 3339).
created_toNoFilter to incidents created on or before this ISO date or datetime.
sitesNoFilter to incidents at any of these site names (use swsd_list_sites to discover).
departmentsNoFilter to incidents in any of these department names.
assigned_to_groupNoFilter to incidents assigned to this group ID. Use swsd_list_groups to find the ID. NOTE: this is GROUP id, not user id.
state_is_notNoNegative state filter: exclude incidents in any of these states (e.g. ["Resolved", "Closed"] to see only open work).
sort_byNoSort key. Default is SWSD-side (typically updated_at desc).
sort_orderNoSort direction. Use uppercase per SWSD convention.
queryNoFree-text search across incident title and description. Same async-indexing caveat as solution search — just-created tickets may not appear for a few minutes.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
incidentsYes
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. NOTE: assignee_email / requester_email are applied client-side; everything else is server-side.
scanYesHonest accounting of what was scanned vs matched.
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint. Description adds crucial context: which filters are client-side (email fields) with a verification date, server-side behavior, pagination caps, sorting defaults. No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is well-structured, front-loaded with key info, and avoids fluff. Could be more bullet-pointed for readability, but it's efficient for its length and content.

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 19 parameters and 100% schema coverage, description covers all critical behavioral aspects: filtering, pagination, relationship to detail endpoint, client-side caveats, and security notes. Output schema mentioned but not needed in description.

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%, so baseline is 3. Description adds significant value: explains client-side filtering for email fields, updated_within convenience alias, OR-ing of multiple values, group ID vs user ID, and sort defaults. Compensates 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?

Clearly states the tool lists SWSD incidents with structured filters and pagination, distinguishes from swsd_get_incident for full detail, and explains the compact summary output. Very specific and helpful.

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 describes when to use this tool (list incidents) vs. alternatives (swsd_get_incident for detail). Also explains filter behavior (client-side vs server-side) and OR semantics.

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