Snipe-IT MCP Server

asset_maintenance

Destructive

Create, track, update, and complete maintenance records for assets, with filtering and search to keep service history organized.

Instructions

Manage maintenance records for assets.

Operations:

create: Create a maintenance record for an asset (requires asset_id and maintenance_data)
list: List maintenance records, optionally filtered by asset_id, search, or completed
get: Get a single maintenance record by maintenance_id
update: Update a maintenance record (requires maintenance_id and update_data)
delete: Delete a maintenance record (requires maintenance_id)
complete: Mark a maintenance record complete (requires maintenance_id; Snipe-IT v8.7+)

Returns: dict: Result of the operation including success status and data

Input Schema

TableJSON Schema

Name	Required	Description
`note`	No	Completion note (for complete action)
`limit`	No	Number of results to return (for list action)
`action`	Yes	The maintenance operation to perform
`offset`	No	Number of results to skip (for list action)
`search`	No	Search query (for list action)
`asset_id`	No	Asset ID (required for create; optional filter for list)
`completed`	No	Filter by completion state (for list action)
`update_data`	No	Fields to change (required for update action)
`maintenance_id`	No	Maintenance record ID (required for get, update, delete, complete)
`maintenance_data`	No	Maintenance record data (required for create action)

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed20 schema fields changedv1.6.1Aug 24, 2026

removedInput schema / properties / action / const
```
Removed value: -"create"
```

changedInput schema / properties / action / description

Previous value: -"The maintenance operation to perform (currently only create is supported)"New value: +"The maintenance operation to perform"

addedInput schema / properties / action / enum

Added value: +[
+  "create",
+  "list",
+  "get",
+  "update",
+  "delete",
+  "complete"
+]

addedInput schema / properties / asset_id / anyOf

Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / asset_id / default
```
Added value: +null
```

changedInput schema / properties / asset_id / description

Previous value: -"Asset ID"New value: +"Asset ID (required for create; optional filter for list)"

removedInput schema / properties / asset_id / type
```
Removed value: -"integer"
```

addedInput schema / properties / completed

Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Filter by completion state (for list action)"
+}

addedInput schema / properties / limit

Added value: +{
+  "default": 50,
+  "description": "Number of results to return (for list action)",
+  "type": "integer"
+}

addedInput schema / properties / maintenance_data / anyOf

Added value: +[
+  {
+    "description": "Model for asset maintenance records.",
+    "properties": {
+      "asset_improvement": {
+        "description": "Type of maintenance/improvement",
+        "type": "string"
+      },
+      "completion_date": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Completion date (YYYY-MM-DD)"
+      },
+      "cost": {
+        "anyOf": [
+          {
+            "type": "number"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Maintenance cost"
+      },
+      "notes": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Maintenance notes"
+      },
+      "start_date": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Start date (YYYY-MM-DD)"
+      },
+      "supplier_id": {
+        "description": "Supplier ID",
+        "type": "integer"
+      },
+      "title": {
+        "description": "Maintenance title",
+        "type": "string"
+      }
+    },
+    "required": [
+      "asset_improvement",
+      "supplier_id",
+      "title"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / maintenance_data / default
```
Added value: +null
```

removedInput schema / properties / maintenance_data / properties

Removed value: -{
-  "asset_improvement": {
-    "description": "Type of maintenance/improvement",
-    "type": "string"
-  },
-  "completion_date": {
-    "anyOf": [
-      {
-        "type": "string"
-      },
-      {
-        "type": "null"
-      }
-    ],
-    "default": null,
-    "description": "Completion date (YYYY-MM-DD)"
-  },
-  "cost": {
-    "anyOf": [
-      {
-        "type": "number"
-      },
-      {
-        "type": "null"
-      }
-    ],
-    "default": null,
-    "description": "Maintenance cost"
-  },
-  "notes": {
-    "anyOf": [
-      {
-        "type": "string"
-      },
-      {
-        "type": "null"
-      }
-    ],
-    "default": null,
-    "description": "Maintenance notes"
-  },
-  "start_date": {
-    "anyOf": [
-      {
-        "type": "string"
-      },
-      {
-        "type": "null"
-      }
-    ],
-    "default": null,
-    "description": "Start date (YYYY-MM-DD)"
-  },
-  "supplier_id": {
-    "description": "Supplier ID",
-    "type": "integer"
-  },
-  "title": {
-    "description": "Maintenance title",
-    "type": "string"
-  }
-}

removedInput schema / properties / maintenance_data / required

Removed value: -[
-  "asset_improvement",
-  "supplier_id",
-  "title"
-]

removedInput schema / properties / maintenance_data / type
```
Removed value: -"object"
```

addedInput schema / properties / maintenance_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Maintenance record ID (required for get, update, delete, complete)"
+}

addedInput schema / properties / note

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Completion note (for complete action)"
+}

addedInput schema / properties / offset

Added value: +{
+  "default": 0,
+  "description": "Number of results to skip (for list action)",
+  "type": "integer"
+}

addedInput schema / properties / search

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Search query (for list action)"
+}

addedInput schema / properties / update_data

Added value: +{
+  "anyOf": [
+    {
+      "description": "Model for partial updates to maintenance records (all fields optional).",
+      "properties": {
+        "asset_improvement": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null,
+          "description": "Type of maintenance/improvement"
+        },
+        "completion_date": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null,
+          "description": "Completion date (YYYY-MM-DD)"
+        },
+        "cost": {
+          "anyOf": [
+            {
+              "type": "number"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null,
+          "description": "Maintenance cost"
+        },
+        "is_warranty": {
+          "anyOf": [
+            {
+              "type": "boolean"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null,
+          "description": "Whether covered under warranty"
+        },
+        "notes": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null,
+          "description": "Maintenance notes"
+        },
+        "start_date": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null,
+          "description": "Start date (YYYY-MM-DD)"
+        },
+        "supplier_id": {
+          "anyOf": [
+            {
+              "type": "integer"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null,
+          "description": "Supplier ID"
+        },
+        "title": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null,
+          "description": "Maintenance title"
+        }
+      },
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Fields to change (required for update action)"
+}

changedInput schema / required

Previous value: -[
-  "action",
-  "asset_id",
-  "maintenance_data"
-]New value: +[
+  "action"
+]

First observedv1.6.0Aug 2, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already flag destructive behavior, and the description aligns by listing the delete operation explicitly. It adds useful behavior beyond the schema, such as the Snipe-IT v8.7+ version dependency for the complete action and a concise return contract. It does not contradict annotations.

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?

The description is compact and well-structured, with a leading purpose sentence followed by a tight bullet list of operations. Each operation is one line and includes only necessary conditions. There is no filler or duplication.

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?

For a multi-action dispatcher with ten parameters, the description provides a complete operation inventory, per-action parameter assignments, and the output type. The schema covers the remaining details, and the presence of an output schema means return values are fully documented. An agent here needs the information to select and invoke the correct action is present.

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%, so the schema already documents each parameter's meaning, defaults, and action-specific requirements. The description restates which parameters are required for which action but does not add meaning beyond that. This meets the baseline for fully covered schemas.

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 opens with a specific verb and resource: 'Manage maintenance records for assets.' It then enumerates all six operations, each with a clear action and target record. This clearly distinguishes the tool from asset-related siblings like manage_assets or asset_licenses.

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?

The description clearly establishes when to use the tool and shows the functional context for each action, including action-specific requirements like asset_id for create and maintenance_id for get/update/delete/complete. It does not explicitly exclude alternatives, but no sibling tool covers maintenance records, so the usage context is sufficiently clear.

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