Skip to main content
Glama
Mouser MCP

Mouser MCP

by RainnWorks

post_cart_items_update

Destructive

Updates cart items in Mouser by part number and quantity, enabling MCP clients to change quantities or packaging choices for existing cart lines.

Instructions

[MouserCart] POST /api/v{version}/cart/items/update Updates the cart items sent in with the request.

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_update"
  }
}

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.4/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 safety profile is partly covered. The description adds nothing about what gets destroyed: it is silent on whether the submitted CartItems replace the whole cart line-item set, on permission or auth requirements, and on what the response contains. For a destructive mutation with no output schema, that is a meaningful 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?

It is short and front-loaded, but the raw route string '[MouserCart] POST /api/v{version}/cart/items/update' duplicates what the name and schema already convey, and the second sentence rephrases the first rather than adding information.

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?

For a destructive, nested-object mutation with four parameters and no output schema, the definition should state the replace-vs-merge semantics and the expected result. Neither is present, leaving the agent unable to call it confidently without inferring behavior.

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

Parameters2/5

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

Schema description coverage is 75%, with countryCode, currencyCode and version documented in the schema. The description adds no meaning to the nested CartItemRequest fields (Quantity, PackagingChoice, CustomerPartNumber) and does not resolve whether Quantity is an absolute value or a delta, so it fails to compensate for the coverage and ambiguity gap at this nesting depth.

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

Purpose3/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 ('Updates the cart items') and echoes the endpoint, so the agent knows it mutates cart items. But 'updates the cart items sent in with the request' is close to circular: it does not say whether quantities are replaced or incremented, or whether items omitted from the payload survive. Siblings such as post_cart_items_insert and post_cart_item_remove are not differentiated beyond the name.

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 mention of prerequisites such as a valid CartKey, and no reference to alternative tools for adding or removing items. The agent must infer the insert-vs-update distinction from the tool name alone.

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