inventree-mcp

Overview Schema Source Related Servers Discussions Admin

build_order

Create, update, allocate, complete, or cancel manufacturing build orders, and retrieve order details with search and pagination.

Instructions

Manufacturing build order management in InvenTree.

Operations: Read: list, get, get_outputs, get_lines Write: create, update, allocate, complete, cancel

Args: operation: One of the operations listed above. pk: Build order ID. data: Dict of fields for create/update/complete. items: List of allocation dicts for allocate (e.g. [{"stock_item": 1, "quantity": 5, "build_line": 3}]). search: Text search filter for list. limit: Max results (default 25). offset: Pagination offset.

Returns: JSON string with build order data or {"error": "..."}.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`operation`	Yes
`pk`	No
`data`	No
`items`	No
`search`	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

A3.8/5.0

Behavior4/5

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

The description discloses the supported operations (read/write) and the meaning of arguments like pk, data, items, etc. It explains the return format (JSON string). Annotations indicate readOnlyHint=false and destructiveHint=false, and the description does not contradict them; it adds context about mutation operations.

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 structured with sections (Operations, Args, Returns) and is front-loaded with the purpose. While it is moderately long, every sentence adds value without being overly verbose.

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

Completeness3/5

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

Given the complexity (7 parameters, nested objects, multiple operations) and that an output schema is implied but not provided, the description covers basic functionality. However, it lacks details on the exact structure of returned data for each operation and potential error conditions beyond a generic error string.

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?

With 0% schema coverage, the description compensates by explaining each parameter: operation (list of values), pk (build order ID), data (dict for create/update/complete), items (list of allocation dicts with example), search (text filter), limit (default 25), offset (pagination). This adds significant meaning beyond the schema.

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 clearly states it is for 'Manufacturing build order management in InvenTree' and lists specific read and write operations. It distinguishes itself from sibling tools by focusing on build orders, which are separate from parts, stock, purchase orders, etc.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not provide explicit guidance on when to use this tool versus alternative tools. While it lists the operations it supports, there is no comparison or recommendation relative to sibling tools like 'part' or 'stock'.

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

Deploy Server