Skip to main content
Glama
Mouser MCP

Mouser MCP

by RainnWorks

post_cart

Destructive

Replaces the contents of a Mouser cart with the provided items, deleting any part numbers not included in the request.

Instructions

[MouserCart] POST /api/v{version}/cart Updates the entire cart. If any part numbers are not included with the request, they will be deleted.

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

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

A3.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, but the description adds the crucial detail of *what* gets destroyed: any part number absent from the request is deleted. That is exactly the replacement-semantics information an agent needs before calling. It stops short of covering auth requirements or what the response contains.

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 sentences with the destructive caveat front-loaded right after the purpose. The endpoint path prefix is redundant noise but costs little.

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 nested-object mutation with no output schema, the definition covers the most dangerous behavior but omits what the call returns (presumably the resulting cart), whether quantities replace or accumulate, and any auth/permission prerequisites. Adequate to call safely, not complete.

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% and the schema already documents version, countryCode, and currencyCode, while the nested CartItems fields carry their own constraints. The description adds no parameter-level meaning (e.g. how CartKey is obtained or when to supply countryCode), so it neither compensates for the gap nor detracts.

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 ('Updates the entire cart') and the word 'entire' signals full-replacement semantics, which implicitly separates it from the item-level siblings (post_cart_items_update, post_cart_item_remove). It does not name any alternative explicitly, so differentiation is inferred rather than stated.

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 implied rather than stated: 'Updates the entire cart' plus the deletion warning tells an agent this is a wholesale replace, and the deletion clause warns against careless use. However, there is no explicit when-to-use guidance or pointer to the item-level insert/update/remove tools for partial edits.

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