Skip to main content
Glama
Mouser MCP

Mouser MCP

by RainnWorks

post_cart_update_schedule

Destructive

Updates scheduled delivery dates for cart items to adjust release timing for specific Mouser part numbers before order placement.

Instructions

[MouserCart] POST /api/v{version}/cart/update/schedule Allows updating schedule delivery(s) 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": {
      "request": "<request>"
    },
    "name": "post_cart_update_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYes
versionNoAPI version. Defaults to 1.1

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/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 covered, but the description adds nothing beyond that. It does not say whether updating a part's schedule replaces existing scheduled releases or merges with them — a critical distinction for a destructive write — nor does it mention auth needs or any failure conditions.

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 API area, route, and purpose front-loaded; no filler or repetition. It is efficient, though the route line is largely redundant with the tool name and the brevity comes at the cost of substance rather than from tight editing.

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 mutation with a deeply nested request object and no output schema, the description is far too thin. An agent cannot determine the shape or replacement semantics of the scheduled releases it must submit, which is the core knowledge needed to call this tool correctly.

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?

Two parameters with 50% schema description coverage: only 'version' has a documented default, while the entire nested request body (CartKey, ScheduleCartItems, MouserPartNumber, ScheduledReleases) is unexplained in both schema and description. The meaning of the key/value pairs inside ScheduledReleases (presumably date-to-quantity) is left entirely to guesswork, so the description does not compensate 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?

The description names a specific verb ('updating') and resource ('schedule delivery(s) for cart items'), and the bracketed tag plus route identify the API area. It is clear what the tool does, but it never contrasts itself with the nearby 'insert_schedule' or 'deleteall_schedule' operations, so the agent must infer the boundary between scheduling and updating.

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 and no mention of the alternatives for schedule manipulation in the sibling set. Prerequisites are also unstated: the caller is not told that a cart key must already exist or that the cart must contain the affected items.

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