Skip to main content
Glama
Sign In
swsd-mcp

swsd-mcp

by mikimatsub
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

swsd_get_catalog_item

Read-onlyIdempotent

Retrieve a SWSD catalog item by id to view its form variables, so you know which fields and options to populate when submitting a service request.

Instructions

Get a single SWSD catalog item by id, including its variables (the form schema for service requests). Use the variables to know which fields to populate when submitting a service request. Each variable has an id (pass through to the create-service-request tool as custom_field_id), a name, a kind (free_text / drop_down_menu / multi_select / date / user / null), and options (newline-separated allowed values for dropdowns). The full top-level item is passed through for power users (description, category, etc.).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "swsd_get_catalog_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCatalog item id from swsd_list_catalog_items.

Output Schema

NameRequiredDescriptionDefault
itemYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv3.3.0
    • addedOutput schema / properties / item / additionalProperties
      Added value: +{}
    • removedOutput schema / properties / item / allOf
      Removed value: -[
-  {
-    "additionalProperties": {},
-    "propertyNames": {
-      "type": "string"
-    },
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "id": {
-        "maximum": 9007199254740991,
-        "minimum": -9007199254740991,
-        "type": "integer"
-      },
-      "variables": {
-        "items": {
-          "additionalProperties": false,
-          "properties": {
-            "field_type": {
-              "maximum": 9007199254740991,
-              "minimum": -9007199254740991,
-              "type": "integer"
-            },
-            "helptext": {
-              "type": "string"
-            },
-            "id": {
-              "maximum": 9007199254740991,
-              "minimum": -9007199254740991,
-              "type": "integer"
-            },
-            "kind": {
-              "type": "string"
-            },
-            "name": {
-              "type": "string"
-            },
-            "options": {
-              "type": "string"
-            },
-            "required": {
-              "type": "string"
-            }
-          },
-          "required": [
-            "id",
-            "name"
-          ],
-          "type": "object"
-        },
-        "type": "array"
-      }
-    },
-    "required": [
-      "id"
-    ],
-    "type": "object"
-  }
-]
    • addedOutput schema / properties / item / properties
      Added value: +{
+  "id": {
+    "maximum": 9007199254740991,
+    "minimum": -9007199254740991,
+    "type": "integer"
+  },
+  "variables": {
+    "items": {
+      "additionalProperties": false,
+      "properties": {
+        "field_type": {
+          "maximum": 9007199254740991,
+          "minimum": -9007199254740991,
+          "type": "integer"
+        },
+        "helptext": {
+          "type": "string"
+        },
+        "id": {
+          "maximum": 9007199254740991,
+          "minimum": -9007199254740991,
+          "type": "integer"
+        },
+        "kind": {
+          "type": "string"
+        },
+        "name": {
+          "type": "string"
+        },
+        "options": {
+          "type": "string"
+        },
+        "required": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "id",
+        "name"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  }
+}
    • addedOutput schema / properties / item / required
      Added value: +[
+  "id"
+]
    • addedOutput schema / properties / item / type
      Added value: +"object"
  2. 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"
  3. First observedv2.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so safety is covered; the description adds value by disclosing the shape of the `variables` payload and the meaning of each field (`id`, `name`, `kind`, `options`). It also notes the full top-level item is returned 'for power users', which tells the agent to expect extra fields beyond variables.

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?

Purpose is front-loaded in the first clause, followed by the variable semantics that justify the call. The enumeration of `kind` values is dense but earns its place by telling the agent what values to expect; a slightly tighter phrasing could have trimmed the parenthetical list.

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?

An output schema exists, yet the description still summarizes the returned variable structure and its downstream mapping to `custom_field_id`, which is exactly the context an agent needs to chain into service-request creation. Nothing required for correct invocation is missing.

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 description coverage is 100% and the single `id` parameter is documented as coming from swsd_list_catalog_items, so the schema carries the load. The description adds no format or edge-case detail about `id` itself, making baseline 3 appropriate.

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 and resource ('Get a single SWSD catalog item by id') and immediately scopes what is returned ('including its `variables`'). The word 'single' implicitly contrasts with swsd_list_catalog_items, so an agent can distinguish retrieval-by-id from listing without opening the schema.

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?

Explicitly ties the tool to a downstream workflow: 'Use the variables to know which fields to populate when submitting a service request', and names the create-service-request tool for the pass-through id. It lacks an explicit 'do not use this to list items' exclusion, but the retrieval context is clear.

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