logiwa-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOGIWA_EMAIL | No | Your Logiwa account email (used with LOGIWA_PASSWORD to obtain a JWT token). | |
| LOGIWA_BASE_URL | No | Optional API base URL. | https://myapi.logiwa.com |
| LOGIWA_PASSWORD | No | Your Logiwa account password (used with LOGIWA_EMAIL to obtain a JWT token). | |
| LOGIWA_API_TOKEN | No | A pre-issued JWT token. If set, it takes precedence and no login call is made. | |
| LOGIWA_TIMEOUT_MS | No | Optional per-request timeout in milliseconds. | 30000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| logiwa_list_productsA | List products (SKUs) in the Logiwa catalog, paginated. Logiwa list endpoints paginate by page index only — there is no server-side text filter, so page through results to find a SKU, or use logiwa_get_product when you already know the product identifier. Args:
Returns: { title, page, page_size, count, total_count, has_more, next_page, items[] }. Each item includes the product identifier (UUID), sku, name, stock and packaging info. |
| logiwa_get_productA | Get the full detail of a single product by its Logiwa identifier (UUID). Args:
Returns: the product object including SKU, name, description, pricing, packing settings, custom fields and flags. |
| logiwa_create_productA | Create a new product (SKU) in Logiwa. Required: clientIdentifier, sku, name, description, currencyId, isPackagingMaterial, packingSettings. Use logiwa_lookup to resolve clientIdentifier and currency/pack-type values. Provide any additional Logiwa fields (kit components, hazmat, custom fields, etc.) via additional_fields. Returns: the create response from Logiwa (typically the new product identifier / status). |
| logiwa_update_productA | Update an existing product. Provide the product 'identifier' (UUID) to locate it, plus the fields to change. Required by the API: sku, name, description, packingSettings. Send the full intended state of these fields. Provide any other Logiwa fields via additional_fields. Returns: the update response from Logiwa. |
| logiwa_list_inventoryA | List on-hand inventory records with their warehouse locations, paginated. Each record ties a product/SKU to a warehouse, location and on-hand quantity, and carries an 'inventoryIdentifier' UUID used by the add/adjust/remove tools. Args:
Returns: paginated { items[] } where each item includes inventoryIdentifier, sku, warehouse, location and quantity. |
| logiwa_add_inventoryA | Increases the on-hand quantity of an existing inventory record by Identify the record with 'inventoryIdentifier' (UUID) from logiwa_list_inventory. Args:
Returns: the operation result from Logiwa. |
| logiwa_adjust_inventoryA | Adjusts the on-hand quantity of an inventory record to a new value. This overwrites the counted quantity. Identify the record with 'inventoryIdentifier' (UUID) from logiwa_list_inventory. Args:
Returns: the operation result from Logiwa. |
| logiwa_remove_inventoryA | Decreases (removes) Identify the record with 'inventoryIdentifier' (UUID) from logiwa_list_inventory. Args:
Returns: the operation result from Logiwa. |
| logiwa_transfer_inventoryA | Move a quantity of a product between warehouse locations / license plates. Identify the product (productSku or productIdentifier) and the source/target locations. Use codes (human-readable) or identifiers (UUIDs). Resolve values with logiwa_lookup, logiwa_list_warehouses and logiwa_list_warehouse_locations. Args (common):
Returns: the transfer result from Logiwa. |
| logiwa_list_shipment_ordersA | List shipment (outbound / sales) orders, paginated. Args:
Returns: paginated { items[] } where each item includes the order identifier (UUID), code, status, warehouse, customer and dates. |
| logiwa_get_shipment_orderA | Get full detail of one shipment order by its identifier (UUID). Args:
Returns: the shipment order including status, addresses, line products, carrier and tracking info. |
| logiwa_create_shipment_orderA | Create a new shipment (outbound) order. Required: code, shipmentOrderType, shipmentOrderDate (ISO date-time), currencyId, shipmentOrderLineList (>=1 line). Provide customer / shipmentAddress / billingAddress as objects matching the Logiwa API. Resolve type/warehouse/currency values with logiwa_lookup. Any other fields go in additional_fields. Returns: the create response (new order identifier / status). |
| logiwa_update_shipment_orderA | Update an existing shipment order. Provide 'identifier' (UUID) plus the full intended state of the required fields. Required: code, shipmentOrderType, shipmentOrderDate, currencyId, shipmentOrderLineList. Other fields via additional_fields. Returns: the update response from Logiwa. |
| logiwa_cancel_shipment_orderA | Cancel a shipment order by its identifier (UUID). This is a destructive state change. Args:
Returns: the cancellation result. |
| logiwa_ship_shipment_ordersA | Mark one or more shipment orders as shipped (completes fulfillment). Args:
Returns: the ship operation result from Logiwa. |
| logiwa_list_purchase_ordersA | List purchase (inbound) orders, paginated. Args:
Returns: paginated { items[] } where each item includes the PO identifier (UUID), code, vendor, warehouse, status and dates. |
| logiwa_get_purchase_orderA | Get full detail (including line items) of one purchase order by its identifier (UUID). Args:
Returns: the purchase order with vendor, warehouse, dates and line products. |
| logiwa_create_purchase_orderA | Create a new purchase (inbound) order. Required: code, clientIdentifier, vendor, purchaseOrderTypeName, warehouseIdentifier, currencyId, purchaseOrderLineList (>=1 line). Resolve client/warehouse/type/currency with logiwa_lookup and logiwa_list_warehouses. Other fields via additional_fields. Returns: the create response (new PO identifier / status). |
| logiwa_receive_purchase_orderA | Receive stock against a purchase order (records an inbound receipt for one product line). Identify the PO (purchaseOrderCode or purchaseOrderIdentifier), the product (sku), the receiving warehouse and location, and the quantity received. Provide lot/expiry/serial or license-plate details via the typed fields or additional_fields. Args (common):
Returns: the receipt result from Logiwa. |
| logiwa_list_return_ordersA | List return orders (RMAs), paginated. Args:
Returns: paginated { items[] } where each item includes the return order identifier, rmaNumber, related shipment order, warehouse and status. |
| logiwa_create_return_orderA | Create a return order (RMA). Required: rmaNumber, returnOrderProductLineList (>=1 line; each line needs productIdentifier + requestedQuantity). Link to the original sale with shipmentOrderCode or shipmentOrderIdentifier. Resolve product identifiers via logiwa_list_products. Other fields via additional_fields. Returns: the create response (new return order identifier / status). |
| logiwa_cancel_return_orderA | Cancel a return order. Identify it by rmaNumber and the related shipment order / warehouse / client. Args (common):
Returns: the cancellation result. Destructive state change. |
| logiwa_list_warehousesA | List the warehouses configured in the account, paginated. Args:
Returns: warehouses with their identifier (UUID), code and name — used to resolve warehouseIdentifier / warehouse code for other tools. |
| logiwa_list_warehouse_locationsA | List warehouse locations (bins/shelves), paginated. Args:
Returns: locations with their identifier (UUID), code, zone/group and warehouse — used to resolve location codes for inventory transfers and receiving. |
| logiwa_list_customersA | List customers (ship-to parties), paginated. Args:
Returns: customers with identifier, name and contact/address details. |
| logiwa_list_vendorsA | List vendors (suppliers) used on purchase orders, paginated. Args:
Returns: vendors with identifier, name and contact details. |
| logiwa_list_retailersA | List retailers / sales channels configured in the account, paginated. Args:
Returns: retailers with identifier and name. |
| logiwa_report_total_inventoryA | Total (consolidated) on-hand inventory across locations, paginated. Best for "how much of each SKU do we have?". Args:
Returns: consolidated inventory rows per SKU/warehouse with on-hand and available quantities. |
| logiwa_report_shipment_historyA | Historical shipped-line records (outbound fulfillment history), paginated. Args:
Returns: shipment line history with SKU, quantities, order and date information. |
| logiwa_report_receiving_historyA | Historical receipt records (inbound receiving history), paginated. Args:
Returns: receipt history with SKU, quantities, purchase order and date information. |
| logiwa_report_available_to_promiseA | Available-to-promise (sellable) quantities per SKU, paginated. Best for "how many can I still sell?". Args:
Returns: ATP rows per SKU/warehouse with on-hand, allocated and available-to-promise quantities. |
| logiwa_lookupA | Fetch Logiwa reference/lookup data used to resolve names and identifiers needed by other tools (clients, warehouses, order types, product types/groups, pack types, damage/return reasons, carriers, users). Many create/update tools need a clientIdentifier, type name, or currency — use this first to discover valid values. Args:
Returns: the requested lookup list (each entry typically has an identifier and a name), or a category summary. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 32 tools
Every tool targets a distinct resource and action. The three inventory-related reporting tools are clearly differentiated (per-location, consolidated, and ATP), and operations like add/adjust/remove/transfer have unambiguous purposes. No two tools appear to overlap.
All tools follow a consistent logiwa_<verb>_<noun> pattern (e.g., list_products, create_shipment_order, cancel_return_order). The sole exception is logiwa_lookup, but it is still a clear verb and fits the overall style. Naming is predictable and uniform.
At 32 tools, the server exceeds the 25-tool threshold the rubric considers too many. Even though the scope is broad (WMS operations), the high count makes the surface feel heavy and potentially overwhelming for agents.
The server covers the primary workflows: products, inventory, shipment and purchase orders, returns, and reporting. However, there are notable gaps such as no delete operations anywhere, no update or cancel for purchase orders, and no get/update for return orders, which could leave agents with dead ends.