Skip to main content
Glama
Mouser MCP

Mouser MCP

by RainnWorks

post_order

Destructive

Submits a new order when SubmitOrder is true; otherwise returns an order summary for review.

Instructions

[Order] POST /api/v{version}/order Submits a new order if the "SubmitOrder" property is set to true. If the "SubmitOrder" property is set to false, then an order summary will be returned.

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

Input Schema

NameRequiredDescriptionDefault
requestYes
versionNoAPI version. Defaults to 1.1

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already state readOnlyHint=false and destructiveHint=true, but the description adds genuinely non-obvious behavior: the same endpoint either commits an order or returns a read-only summary depending on SubmitOrder. That mode switch materially changes risk, and it is disclosed clearly. It still omits whether a submitted order is reversible, what happens on partial failure, or any auth/rate-limit context.

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 tight sentences with the conditional outcome front-loaded, no filler. The bracketed HTTP path prefix is marginal for an agent and the bracketed tag is redundant, but nothing is verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The nested request object is enormous and there is no output schema, so the description would benefit from noting required fields and the response shape for the summary path. For a mutation tool with only partial parameter documentation, the definition leans on two sentences where more prerequisite detail is needed.

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?

With 50% schema description coverage, the description compensates for one important gap by explaining the SubmitOrder flag's two outcomes, which is buried deep in a nested schema. The version parameter and the large body of required/nested fields (CurrencyCode, CartKey, shipping, payment) get no mention, so meaning is only partly added.

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?

"Submits a new order" is a specific verb plus resource, so an agent knows the core action. It does not differentiate itself from siblings such as post_order_createfromorder, and the leading "[Order] POST /api/v{version}/order" line restates routing rather than purpose.

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?

The description implies the two-mode usage via the SubmitOrder flag (submit vs. return a summary), which is real context for choosing how to call it. However, it never says when to prefer this tool over the sibling order/cart tools, nor what prerequisites (cart already populated, currency set) must hold.

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