Skip to main content
Glama
swsd-mcp

swsd-mcp

by mikimatsub

Related Servers

Alternatives to swsd-mcp

No user-submitted related servers found.

    Related Servers

    TDQS

    A3.6/5.0

    Scored across 52 tools

    Disambiguation3/5

    Most resources (incidents, problems, solutions, users, groups, sites) are cleanly separated, but the incident-listing surface is crowded: swsd_list_incidents, swsd_list_my_incidents, swsd_my_queue, swsd_sla_risk and swsd_ticket_stats all return overlapping incident rows and require careful reading to pick correctly. There is also genuine confusion between swsd_update_task (which takes is_complete) and swsd_update_task_state, and between incident-specific comment tools and the generic record comment tools.

    Naming Consistency4/5

    The dominant pattern is a uniform swsd_verb_noun scheme (swsd_get_incident, swsd_list_users, swsd_create_problem, swsd_update_comment), which makes the set predictable. A minority of tools break the verb-first pattern (swsd_sla_risk, swsd_my_queue, swsd_ticket_stats, swsd_change_calendar, swsd_health_check), but they are still readable and consistently prefixed.

    Tool Count2/5

    52 tools is well beyond a comfortable agent-facing surface for what is essentially one ITSM domain, and many are near-duplicate incident views or thin per-resource getters (get_role, get_site, get_department) that could be collapsed. The size forces the agent to scan a large decision space before every call.

    Completeness3/5

    Incidents have strong lifecycle coverage (create/get/update/state/assign/comments/tasks/time/attachments/audits/SLA), but changes and releases only have read-side helpers (comments, tasks, calendar, audits) with no get/create/update tools. swsd_create_solution and swsd_update_solution are referenced inside swsd_describe_custom_fields and swsd_search_solutions yet do not appear in the tool list, and no delete operations exist anywhere.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data