Snipe-IT MCP Server

component_operations

Checkout components to assets, checkin from assets, and list assets with a component. Manage component quantities and track assignments.

Instructions

Perform checkout/checkin operations on components.

Components can be checked out to assets (not users). Each checkout decrements the available quantity.

Operations:

checkout: Checkout component(s) to an asset (requires checkout_data with assigned_to asset ID)
checkin: Checkin component(s) from an asset (requires checkout_id)
list_assets: List all assets that have this component checked out

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

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": {
      "action": "<action>",
      "component_id": "<component_id>"
    },
    "name": "component_operations"
  }
}

Input Schema

Name	Required	Description
`action`	Yes	The operation to perform on the component
`checkout_id`	No	Component asset ID from checkout record (required for checkin)
`component_id`	Yes	Component ID
`checkout_data`	No	Checkout data (required for checkout action)

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

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 indicate this is not read-only and not destructive. The description adds a key behavioral detail beyond annotations: 'Each checkout decrements the available quantity.' It also discloses the return structure as a dict. This is valuable context, though it omits potential failure modes or authorization requirements, keeping it at a 4.

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 well-structured with a brief intro, a bulleted list of operations, and a return type line. It is not padded with fluff, though the 'Returns:' section could be trimmed since output schema already provides that detail. Still, it is efficient and easy to scan.

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?

For a tool with 4 parameters, 3 actions, and an output schema, the description provides enough context to understand the tool's role and how to invoke each action. It covers purpose, operations, parameter requirements, and returns. It could mention edge cases or prerequisites (e.g., items must be in stock), but it is largely complete.

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%, so all parameters are already documented. The description adds value by mapping parameters to actions: it specifies that checkout requires checkout_data, checkin requires checkout_id, and list_assets needs none. This conditional information is not fully captured in the schema, so the description elevates the semantics.

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: 'Perform checkout/checkin operations on components.' It then enumerates three distinct operations (checkout, checkin, list_assets), making its purpose unmistakable. It also distinguishes itself from component management tools by focusing on operational actions rather than CRUD management.

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 provides clear context for when to use each operation by stating required inputs: checkout requires checkout_data, checkin requires checkout_id, and list_assets needs no extra. However, it does not explicitly compare with sibling tools or state when not to use this tool, so it stops short of a full 5.

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