Skip to main content
Glama
Mouser MCP

Mouser MCP

by RainnWorks

post_cart_insert_schedule

Destructive

Schedule delivery releases for Mouser cart items by submitting part numbers and scheduled quantities to manage cart delivery timing.

Instructions

[MouserCart] POST /api/v{version}/cart/insert/schedule Allows adding 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_insert_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 flag readOnlyHint=false and destructiveHint=true, but the description says nothing about the destructive semantics: whether existing schedules are replaced or appended, whether authentication/session cart state is required, or whether the operation can be undone. For a destructive mutation this is a real gap.

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 lean sentences with the endpoint identifier front-loaded and no filler. The bracket-tag plus raw path is somewhat redundant with the tool name, but it is efficient overall.

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?

A destructive, nested-object mutation with no output schema and no return-value or error information. The description does not tell the agent what a successful response confirms or what happens to prior schedules, leaving too much unknown for a write operation.

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 coverage is only 50%, so the description should explain the parameters, yet it mentions none. Critically, the nested ScheduledReleases key/value pairs (a string key mapped to an int32) — which drive the actual scheduling behavior — are left completely undefined in both schema and description.

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: adding scheduled deliveries for cart items, backed by an explicit endpoint path. It implicitly contrasts with the sibling update/delete-schedule tools through the word 'adding', though it never names them.

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 guidance on when to use this versus post_cart_update_schedule or post_cart_deleteall_schedule, and no prerequisites such as having a cart key or existing cart items. The agent must infer the workflow from the endpoint name alone.

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