Skip to main content
Glama
Sign In
swsd-mcp

swsd-mcp

by mikimatsub
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

swsd_list_departments

Read-onlyIdempotent

Retrieve SWSD departments (id, name, description) to validate department names before creating or updating incidents. Supports pagination and name filtering.

Instructions

List SWSD departments (organizational divisions). Returns id, name, description. Use this to validate department_name before incident write tools.

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (1-indexed).
queryNoOptional name substring filter.
per_pageNoResults per page (1-100).

Output Schema

NameRequiredDescriptionDefault
paginationYes
departmentsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv3.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changedv2.3.1
    • addedInput schema / properties / query / maxLength
      Added value: +2000
  3. First observedv2.1.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safe read-only nature is covered. The description adds useful context by naming the fields returned and the validation workflow. However, it does not mention pagination behavior or rate limits, which would be valuable given the page/per_page params.

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 the action and resource, followed by the return fields and usage guidance. No waste.

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?

Complete enough for a simple list tool with a defined purpose. The only gap is pagination behavior, but the annotations already cover the safety profile and the output schema exists. The description does its job without needing to explain return values.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema fully documents page, query, and per_page. The description adds no parameter-specific syntax or format details beyond what the schema provides. Baseline 3 is appropriate when the schema handles all parameter documentation.

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?

States a specific verb+resource ('List SWSD departments') and parenthetically clarifies scope with 'organizational divisions', immediately distinguishing it from sibling list tools like swsd_list_groups or swsd_list_roles.

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 the use case: 'Use this to validate department_name before incident write tools.' This tells the agent exactly when to invoke this tool versus others, and ties it to a concrete workflow.

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

Deploy Server

Other Tools