inventree-mcp

Overview Schema Source Related Servers Discussions Admin

part

Destructive

Create, read, update, delete, and search parts and categories in InvenTree, with access to stock, BOM, suppliers, parameters, and other related data.

Instructions

Part & category management in InvenTree.

Operations: Read: list, get, get_stock, get_bom, get_bom_usage, get_suppliers, get_manufacturers, get_parameters, get_parameter_templates, get_test_templates, get_related, get_builds, get_internal_prices, get_sale_prices, list_categories, get_category, get_category_parameters Write: create, update, create_category Delete: delete

Args: operation: One of the operations listed above. pk: Part or category ID (required for get/update/delete and sub-queries). data: Dict of fields for create/update (e.g. {"name": "Seal Kit", "category": 5}). search: Text search filter for list/list_categories. category: Category ID filter for list. limit: Max results for list (default 25). offset: Pagination offset for list.

Returns: JSON string with part/category data or {"error": "..."}.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`operation`	Yes
`pk`	No
`data`	No
`search`	No
`category`	No
`limit`	No
`offset`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 3, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already indicate destructiveHint=true and not read-only. The description adds detail by listing destructive operations ('delete') and explains return format ('JSON string with part/category data or error'), providing extra behavioral context beyond annotations.

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 leading purpose sentence, followed by operations list, arguments, and returns. It is front-loaded and relatively concise, though could be slightly trimmed without losing clarity.

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?

Given the tool's complexity (7 parameters, multiple operation types), the description covers all aspects: operations, required parameters, data format, pagination, and return type. An output schema exists, so no need to detail return values further.

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 description coverage is 0%, but the description adds meaning for each parameter: explains operation values (though not full enum), pk usage, data dict for create/update, search filter, pagination limit/offset. This compensates well for the missing schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool is for 'Part & category management in InvenTree' and enumerates specific operations (read, write, delete), but does not explicitly differentiate from sibling tools like stock or company.

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 lists operation types (Read, Write, Delete) and explains when to use each (e.g., 'pk required for get/update/delete'). It gives context for parameters but does not specify when not to use this tool or suggest alternatives.

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

Deploy Server