Skip to main content
Glama
Mouser MCP

Mouser MCP

by RainnWorks

post_cart_item_remove

Destructive

Removes a Mouser part from a cart by part number, helping you correct or update cart contents.

Instructions

[MouserCart] POST /api/v{version}/cart/item/remove Removes an item from the cart based on mouser part number.

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": {
      "cartKey": "<cartKey>",
      "mouserPartNumber": "<mouserPartNumber>"
    },
    "name": "post_cart_item_remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
cartKeyYes
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.
mouserPartNumberYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/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 adds the removal mechanism (keyed on Mouser part number), but it does not say whether the entire line is dropped or only one unit, whether the operation is idempotent, or whether pricing/totals are recalculated — meaningful gaps for a destructive mutation.

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 action stated up front and no filler. The raw endpoint path/prefix is low-value metadata that doesn't help tool selection, keeping it from a 5.

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 destructive 5-parameter mutation with no output schema, the definition covers the core action but omits return behavior (confirmation, updated cart totals), idempotency, and the semantics of cartKey. It is minimally sufficient to call correctly but 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 coverage is 60%: version, countryCode and currencyCode are documented in the schema, while cartKey and mouserPartNumber are not. The description only adds that mouserPartNumber is the key identifying the item to remove; cartKey's role in scoping the cart is left entirely to inference, so it partially but not fully 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?

States a specific verb and resource ("Removes an item from the cart") plus the selector ("based on mouser part number"), which clearly separates it from siblings such as post_cart_items_update or post_cart_deleteall_schedule. It stops short of naming any sibling explicitly, so a 4 rather than a 5.

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?

No when-to-use or when-not-to-use guidance: nothing tells the agent to prefer this over post_cart_deleteall_schedule when clearing the whole cart, or over post_cart_items_update when only changing quantity. Prerequisites (a valid cartKey, an existing cart) are never stated; usage is only implied by the purpose sentence.

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