Skip to main content
Glama
hvkshetry

inventree-mcp

by hvkshetry

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
NameRequiredDescriptionDefault
operationYes
pkNo
dataNo
itemsNo
searchNo
limitNo
offsetNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Annotations indicate non-read-only, non-destructive, and open-world behavior. The description adds operations and return format, but does not detail mutation effects, error handling, or permission needs. Moderate improvement over 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 sections, but the 'Operations' list is somewhat redundant given the 'operation' parameter. Remaining text is efficient and front-loaded.

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?

Covers all parameters and return format, but lacks per-operation required parameters (e.g., pk for get/update). Output schema exists, reducing need for detailed return field descriptions, but guidance on parameter combinations is missing.

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 description coverage, the description fully explains all 7 parameters, including examples for 'items'. This provides essential meaning that the schema lacks.

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 identifies the tool as 'building order management in InvenTree', listing specific read/write operations. Sibling tools like 'part' or 'stock' are distinct domains, so this tool is easily distinguishable.

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

Usage Guidelines3/5

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

The description lists operations but does not explicitly guide when to use this tool vs siblings or which operation to pick. Context from sibling names implies domain-specific usage, but no situational guidance is provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/hvkshetry/inventree-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server