Skip to main content
Glama
Mouser MCP

Mouser MCP

by RainnWorks

post_order_item_createcartfromorder

Destructive

Creates a new cart from an existing order by order number, optionally applying country and currency codes to set shipping rules and cart pricing.

Instructions

[MouserCart] POST /api/v{version}/order/item/CreateCartFromOrder Creates new cart from an order.

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": {
      "orderNumber": "<orderNumber>"
    },
    "name": "post_order_item_createcartfromorder"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the write/mutating nature is covered. The description adds nothing beyond that: it does not say whether the source order is consumed or modified, whether the operation is idempotent or repeatable, or what the destructive aspect actually destroys. For a tool flagged destructive, that is a significant gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The text is short and front-loaded, but the first line is a raw REST endpoint and tag ('[MouserCart] POST /api/v{version}/order/item/CreateCartFromOrder') that adds no decision-relevant information for an agent, while the one sentence of actual meaning is minimal.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a destructive, non-read-only mutation with no output schema, and the description does not explain what the resulting cart contains, what happens to the originating order, or what errors to expect. Given the complexity and the destructive annotation, the description is under-specified.

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 coverage is 75%, so countryCode, currencyCode, and version already carry useful descriptions. The description adds no meaning beyond the schema and leaves orderNumber (the sole required parameter) undocumented in both places. Baseline 3 is appropriate given the schema does most of the work.

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 names a specific verb and resource: it creates a new cart from an existing order. That is clear enough to act on, but it offers no differentiation from the similarly named sibling post_order_createfromorder, so an agent cannot tell the two apart from the description alone.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites (e.g., the order must exist and be in a state that permits re-carting), and no reference to alternatives such as post_order_createfromorder or post_cart. The agent must infer the invocation context.

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