Snipe-IT Copilot MCP

inventory_write

Idempotent

Create or update Snipe-IT accessories, components, and consumables with explicit fields, once required IDs are known. Does not assign, check in/out, or delete inventory.

Instructions

Create or update one accessory, component, or consumable using explicit fields. Use for ordinary inventory record writes after required IDs are known. This tool cannot assign, check in, check out, or delete inventory.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`qty`	No
`name`	No
`notes`	No
`serial`	No
`item_id`	No
`min_amt`	No
`company_id`	No
`action_name`	Yes
`category_id`	No
`location_id`	No
`supplier_id`	No
`model_number`	No
`order_number`	No
`purchase_cost`	No
`purchase_date`	No
`inventory_type`	Yes
`manufacturer_id`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`item`	No
`message`	No
`success`	Yes
`error_code`	No
`validation_errors`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 5, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations declare the safety profile (readOnly=false, idempotent=true, destructive=false, openWorld=true), and the description adds the capability boundary by listing the operations it deliberately omits. It does not disclose auth requirements, what an update overwrites, or error behavior, so it adds real value but not exhaustive behavioral detail.

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?

Three tight sentences, no redundancy; the core purpose and the capability boundary are front-loaded so the agent gets the essential routing information immediately.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists so return values need not be explained, but for a 17-parameter write tool with 0% schema coverage the definition leaves parameter usage almost entirely undocumented. Given the tool's complexity, a description this thin is materially incomplete.

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

Parameters1/5

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

Schema description coverage is 0% across 17 parameters and the description contributes no parameter-level meaning beyond the phrase "explicit fields" and a vague "required IDs are known." With zero schema documentation and 17 params, the description fails to compensate, and the "required IDs" phrasing even misleads since only inventory_type and action_name are required while the rest carry defaults.

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 pair (create or update) and a specific resource (one accessory, component, or consumable), and explicitly names the write actions it does NOT perform (assign, check in, check out, delete), which cleanly separates it from siblings like inventory_lifecycle and delete_resource.

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?

"Use for ordinary inventory record writes after required IDs are known" gives clear context, and the closing sentence enumerates the excluded operations, implying the alternative tools. It stops short of naming those alternatives or stating prerequisites/permission needs explicitly, so it is strong but not fully prescriptive.

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