Skip to main content
Glama
MSPbotsAI

ingrammicro-mcp

by MSPbotsAI

ingrammicro_create_cloud_order

Destructive

Place a cloud-subscription order or convert a validated quote into a real order, returning a confirmation number for asynchronous processing.

Instructions

Place a cloud-subscription order, or convert an existing Quote (Quote-to-Order / Configure-to-Order) into a real order. Asynchronous: this call only returns a confirmationNumber acknowledging receipt — Ingram Micro pushes the actual order result (success or error) later via its own webhook, not in this response.

    For standard stocked/direct-ship/licensing/warranty SKUs (not
    cloud, not quote-based), use ingrammicro_create_order instead.
    Real money against the reseller's net-terms account — no dry-run,
    no credit-card ordering. Always validate a quote first with
    ingrammicro_validate_quote_to_order before passing quote_number
    here.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
linesNoStandard-order line items (ignored in Quote-to-Order mode): [{"customerLineNumber", "ingramPartNumber", "vendorPartNumber", "quantity", "unitPrice", "endUserPrice" (required for export orders), "specialBidNumber", "notes"}]. Required unless quote_number is given.
notesNoOrder header-level notes.
quote_numberNoIngram Micro quote number for Quote-to-Order or Configure-to-Order. When given, any SKU/quantity/price in `lines` is IGNORED — the quote's own details are used instead. Validate it first with ingrammicro_validate_quote_to_order to learn any vendor-mandatory fields to pass here.
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 backordered.
bill_to_address_idNoBilling address suffix from onboarding.
special_bid_numberNoHeader-level special-pricing bid number.
vendor_auth_numberNoVendor authorization number, if the specific vendor requires it.
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_numberNoYour own order number for reference (max 18 chars). Strongly recommended even though not strictly required.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Install Server

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing asynchronous behavior (only returns confirmationNumber, actual result via webhook), real-money impact, and no dry-run capability. This is critical for setting an agent's expectations about side effects. No contradiction with the destructiveHint annotation.

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?

Every sentence carries operational weight: purpose, async caveat, sibling disambiguation, financial warning, and validation prerequisite. There is no filler, and the core action is front-loaded. The length is appropriate for the complexity.

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 13 parameters with zero required fields and a rich schema, the description covers the essential operational context: async receipt, webhook-based results, financial consequences, and quote validation. It does not need to enumerate all parameters because the schema already documents them thoroughly.

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 coverage is 100%, so the baseline is 3. The top-level description adds meaningful context about the quote_number dependency, the need to validate quotes, and the distinction between quote-based and line-item ordering. This supplements the schema's already-strong parameter descriptions.

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 states specific actions: placing a cloud-subscription order or converting a Quote-to-Order/Configure-to-Order into a real order. It also explicitly differentiates itself from ingrammicro_create_order by naming that sibling for standard SKUs. This makes the tool's purpose unambiguous.

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?

Provides explicit when-to-use and when-not-to-use guidance: standard SKUs should use ingrammicro_create_order instead. It also instructs the agent to validate a quote first with ingrammicro_validate_quote_to_order before passing quote_number. This is direct and actionable routing.

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