Skip to main content
Glama
MSPbotsAI

ingrammicro-mcp

by MSPbotsAI

ingrammicro_create_order

Destructive

Places real purchase orders for standard SKUs (stocked, direct-ship, licensing, warranty) on net-terms, returning per-line success/error details and rejected items on partial failure.

Instructions

Place a real purchase order for stocked, direct-ship, licensing, or warranty SKUs. Real money against the reseller's net-terms account — Ingram does not support credit-card API ordering.

    For cloud subscriptions, Quote-to-Order, or Configure-to-Order, use
    ingrammicro_create_cloud_order instead — this tool is for standard
    SKU ordering only. Confirm every SKU/quantity/price with a human
    first; there is no dry-run mode. Returns per-line success/error/
    warning counts and, on partial failure, a rejectedLineItems list
    naming exactly which lines failed and why.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
linesYesOrder line items: [{"customerLineNumber": <unique numeric string, 1-884>, "ingramPartNumber": <Ingram's own SKU, required>, "quantity": <int>, "unitPrice": <optional decimal, not guaranteed>, "specialBidNumber": <optional, line-level pricing bid>, "notes": <optional>}]. Resolve ingramPartNumber via Ingram Micro's own MCP Server's product/catalog search first — this server has no catalog lookup of its own.
notesNoOrder-level notes.
ship_to_infoNoOptional shipping destination override: {"addressId" (Ingram-issued address id from onboarding), "contact", "companyName", "name1", "name2", "addressLine1/2/3", "city", "state", "postalCode", "countryCode", "phoneNumber", "email"}. Omit to ship to the address tied to addressId on the account.
end_user_infoNoOptional end-customer identity, used for pricing/discount purposes: {"endUserId", "contact", "companyName", "name1", "name2", "addressLine1/2/3", "city", "state", "postalCode", "countryCode", "phoneNumber", "email"}.
reseller_infoNoOptional reseller identity/address override: {"resellerId", "companyName", "contact", "addressLine1/2/3", "city", "state", "postalCode", "countryCode", "phoneNumber", "email"}. Omit to use the account's on-file reseller info.
shipment_detailsNoOptional shipping instructions: {"carrierCode", "freightAccountNumber" (bill reseller's own carrier account directly), "shipComplete" ("true"/"C"=hold until all lines ship, "P"=ship-complete per line, "E"=ship-complete across all distributions), "requestedDeliveryDate" (date, not guaranteed), "signatureRequired" (bool), "shippingInstructions"}.
accept_back_orderNoAccept the order even if a line is backordered. Ignored if shipment_details.shipComplete is set.
bill_to_address_idNoBilling address suffix issued during onboarding. Omit for the default.
special_bid_numberNoHeader-level special-pricing bid number from the vendor. Line-level bids in `lines` take precedence.
vendor_auth_numberNoVendor authorization number — REQUIRED for warranty-SKU orders (the specific vendor mandates this; ask Ingram Micro sales which vendors need it). Without it, warranty orders are placed on hold.
additional_attributesNoOptional Ingram-specific flags as [{"attributeName", "attributeValue"}] pairs — e.g. allowPartialOrder, allowDuplicateCustomerOrderNumber, government-order fields (govtProgramType, govtEndUserType, etc). Rarely needed; omit unless a specific Ingram-documented flag is required.
customer_order_numberYesYour own unique PO/order number for this order (max 35 chars). Ingram Micro tracks orders by this, not just its own order number — reuse of a number that already exists is rejected unless allowDuplicateCustomerOrderNumber is set via additional_attributes.
end_customer_order_numberNoThe end customer's own PO number, if any.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Install Server

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already mark the operation as destructive and non-idempotent, and the description meaningfully enlarges on that: real money against net-terms, no credit-card API support, no dry-run mode, and partial-failure behavior via rejectedLineItems. This is exactly the kind of behavioral context the annotations alone cannot convey.

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?

The description is compact and front-loaded with the most important warning: 'Real money... no dry-run mode.' Every sentence earns its place, covering funding constraints, tool routing, approval requirements, and response behavior without redundancy.

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?

For a high-stakes, 13-parameter ordering tool, the description plus fully documented schema and output schema covers scope, exclusions, risk, prerequisites, and post-call outcomes. Nothing essential is missing for an agent to decide whether and how to invoke the tool.

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

Parameters3/5

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

Schema description coverage is 100%, and the schema already documents all 13 parameters in detail, so the description correctly avoids re-explaining them. The description adds process-level context like confirming SKUs with a human, but this is not parameter-specific semantic detail, so the baseline of 3 is appropriate.

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 opens with a specific action and resource: 'Place a real purchase order for stocked, direct-ship, licensing, or warranty SKUs.' It also explicitly names the sibling tool to use instead for cloud/quote/configure-to-order, making differentiation from the large sibling list immediate.

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

Usage Guidelines5/5

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

It gives explicit when-to-use guidance: use this tool for standard SKU ordering, and use ingrammicro_create_cloud_order for cloud subscriptions, Quote-to-Order, or Configure-to-Order. It also prescribes a human-approval step, since there is no dry-run mode.

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

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/MSPbotsAI/ingrammicro-mcp'

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