Skip to main content
Glama
mikimatsub

swsd-mcp

by mikimatsub

swsd_list_my_incidents

Read-onlyIdempotent

List incidents assigned to the authenticated user, supporting filters for state, priority, and more. Handles API limitations by client-side filtering on assignee email.

Instructions

List incidents assigned to the authenticated user. Internally calls swsd_get_me to discover the user's email, then calls /incidents.json with the OTHER server-side filters applied (state, priority, etc.) and narrows the response client-side by assignee.email — because SWSD's /incidents.json endpoint silently ignores assignee_email / requester_email filters (verified 2026-05-08 against the live API: a fake email returns the entire tenant). The client-side filter is the only correct way to scope to a specific user. For broader queries use swsd_list_incidents with assigned_to=<group_id> (group filtering does work server-side).

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.
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 is applied client-side (post-fetch) because SWSD ignores it server-side.
assignee_emailYesThe authenticated user's email used as the assignee filter (applied client-side).
scanYesHonest accounting of the client-side filter: what was scanned vs matched.
Behavior5/5

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

Thoroughly describes internal behavior: calls swsd_get_me to get user email, client-side filter due to API limitation, and verification date. Annotations already mark read-only but description adds essential context about the workaround and potential side effects (e.g., returning entire tenant for fake emails).

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?

The description is fairly long but well-structured: first sentence states purpose, then explains internal behavior, then compares to sibling. Every sentence adds value, though some could be more concise. It front-loads key information.

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 tool's complexity (18 parameters, API limitation, output schema exists), the description is highly complete. It covers the essential behavioral aspect (client-side filtering), error scenarios (fake email test), prerequisite tool mention, and sibling alternative. Missing no critical context.

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 parameter descriptions, so baseline is 3. The description adds value by explaining the overall context (client-side filter) and how parameters like assignee_email are handled, but does not significantly augment individual parameter semantics beyond the 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 incidents assigned to the authenticated user, using a specific verb and resource scope. It distinguishes itself from the sibling tool swsd_list_incidents by noting the limitation of server-side filtering and the client-side workaround.

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 states when to use this tool (for user-specific incidents) and when not ('For broader queries use swsd_list_incidents with assigned_to=<group_id>'). Also explains the API limitation and the internal behavior, providing clear guidance for correct usage.

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