Skip to main content
Glama
Mouser MCP

Mouser MCP

by RainnWorks

post_order_createfromorder

Destructive

Creates a new order by copying an existing order number; set SubmitOrder to true to submit it, or false to return an order summary.

Instructions

[Order] POST /api/v{version}/order/CreateFromOrder Submits a new order from an old order and if the "SubmitOrder" property is set to true. If the "SubmitOrder" property is set to false, then an order summary will be returned.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "request": "<request>",
      "orderNumber": "<orderNumber>"
    },
    "name": "post_order_createfromorder"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYes
versionNoAPI version. Defaults to 1.1
countryCodeNoOptional. If not provided, the billing/shipping address associated with the account will be used to determine country code. If provided, country code will be used to determine shipping rules.
orderNumberYes
currencyCodeNoOptional. If not provided, the default currency code based on the billing/shipping address associated with the account will be used to determine currency code. If provided, currency code will be used to price the cart.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is covered. The description still adds real value by disclosing the conditional branch: SubmitOrder=true submits the order, false returns an order summary only — a meaningful dry-run semantic not expressed anywhere in the schema. It does not mention permissions or whether the source order is altered, which keeps it from a 5.

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?

Short and front-loaded with the endpoint and the core action, then the conditional behavior. The second sentence is grammatically broken ('and if the "SubmitOrder" property is set to true' dangles), which slightly hurts readability but adds no bloat.

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?

For a 5-parameter, deeply nested mutation tool with no output schema, the description covers the action and the commit/preview branch but leaves the return shape unclear (what identifies the new order number, what the summary contains) and does not clarify the source-order semantics. Adequate but with clear gaps.

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?

With 60% schema description coverage, the description's main contribution is explaining the effect of SubmitOrder, whose schema entry carries only a default of false and no description. It says nothing about the orderNumber parameter (source order vs. new order number) or the request wrapper, so it only partially compensates for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource: it submits a new order derived from an existing order (matching the required orderNumber parameter). It is reasonably distinguishable from the sibling post_order (create from scratch), though it never names that sibling explicitly to sharpen the contrast.

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?

Usage is only implied by the required orderNumber and the 'from an old order' phrasing; there is no explicit statement of when to pick this over post_order or post_order_item_createcartfromorder. The one genuinely useful usage signal is the SubmitOrder flag, which effectively documents a preview-vs-commit mode.

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