Skip to main content
Glama
Mouser MCP

Mouser MCP

by RainnWorks

post_cart_deleteall_schedule

Destructive

Deletes all scheduled deliveries for items in a cart by cart key, clearing upcoming delivery schedules in one API call.

Instructions

[MouserCart] POST /api/v{version}/cart/deleteall/schedule Allows deleting all scheduled deliveries for cart items.

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

Input Schema

NameRequiredDescriptionDefault
cartKeyYes
versionNoAPI version. Defaults to 1.1

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known; the description usefully narrows what is destroyed (scheduled deliveries rather than cart items). It does not say whether the deletion is irreversible, whether cart items themselves survive, or what is returned on success, which matters for a destructive bulk operation.

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 core sentence is short and front-loaded, but the leading '[MouserCart] POST /api/v{version}/cart/deleteall/schedule' is restated endpoint noise that adds no decision value. What remains is one efficient clause.

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 two-parameter destructive mutation with no output schema, the definition establishes scope of deletion but leaves the state of cart items, reversibility, and error behavior unaddressed. Adequate to attempt the call, not complete enough to predict its effects confidently.

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 only 50% – version is documented in the schema, but cartKey carries no description and the description adds nothing about its meaning (presumably the cart whose schedules are wiped). The description does not compensate for the coverage gap on the one required parameter.

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 states a specific verb and resource: deletes all scheduled deliveries for cart items, which is more precise than the name alone. It does not, however, distinguish itself from adjacent siblings such as post_cart_item_remove or post_cart_update_schedule, so an agent must infer whether those also affect schedules.

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 statement of when to use this over post_cart_item_remove, post_cart_update_schedule, or post_cart_insert_schedule, and no exclusions or prerequisites such as authentication or cart state requirements. The only usable signal is the phrase 'all scheduled deliveries', which implies bulk scope but not routing guidance.

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