Skip to main content
Glama
Mouser MCP

Mouser MCP

by RainnWorks

post_cart_items_insert

Destructive

Add one or more Mouser part numbers to a cart with quantities and optional packaging choices, enabling order preparation and cart updates.

Instructions

[MouserCart] POST /api/v{version}/cart/items/insert Allows one or more part numbers to be added to the cart

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>"
    },
    "name": "post_cart_items_insert"
  }
}

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.
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.9/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, and the description is consistent with a write, so there is no contradiction. However, it adds almost nothing beyond the safety profile: it does not say whether inserting a part already in the cart merges quantities or overwrites the line, which is exactly the behavior an agent needs given destructiveHint=true, nor does it mention auth or error behavior.

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?

Two short lines with the endpoint tag first and the behavioral sentence front-loaded; nothing is padded. The bracketed route/verb prefix is somewhat redundant with the tool name but is a conventional, low-cost header.

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 state-mutating tool with a nested request object and no output schema, so the description should explain return/confirmation behavior and merge-vs-replace semantics; it does none of that. For a destructiveHint=true cart mutation with four parameters, the definition is too thin to call confidently.

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 75%, so the schema largely documents itself; the description only adds that the request accepts one or more part numbers, mapping to the CartItems array. CartKey, MouserPaysCustomsAndDuties, PackagingChoice, and CustomerPartNumber carry no explanation in the description beyond what the nested schema exposes.

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?

"Allows one or more part numbers to be added to the cart" gives a specific verb (add/insert) and resource (cart items) and calls out batch behavior. It does not name sibling tools such as post_cart_items_update or post_cart_item_remove, so the distinction from a replace/update operation is left implicit, but the intent is still readable.

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 guidance on when to use this instead of post_cart_items_update or post_cart, and no prerequisites are stated (cart key required, account address determining country/currency). The agent must infer usage entirely from the name and schema.

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