Skip to main content
Glama
Mouser MCP

Mouser MCP

by RainnWorks

get_orderhistory_webordernumber

Read-only

Retrieve Mouser order details using a web order number to review items, status, and order information.

Instructions

[MouserOrderHistory] GET /api/v{version}/orderhistory/webOrderNumber Returns order details for the supplied web order 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": {
      "webOrderNumber": "<webOrderNumber>"
    },
    "name": "get_orderhistory_webordernumber"
  }
}

Input Schema

NameRequiredDescriptionDefault
versionNoAPI version. Defaults to 1.1
webOrderNumberYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds nothing beyond that: it doesn't say whether a missing order returns empty or an error, whether results are paginated, or what the payload contains.

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 sentences, front-loaded with the resource and purpose. The endpoint path prefix is mostly noise for an agent but costs little.

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 simple read-only lookup with annotations covering safety and no output schema, the description is minimally adequate. It falls short on the two things that matter for correct invocation: identifier format for webOrderNumber and disambiguation from the sibling order-lookup tools.

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 50% — the version parameter is documented, but webOrderNumber has no schema description. The description only echoes that a web order number is supplied, without stating its expected format (integer identifier vs. a web-style order code), which is the main ambiguity for this 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 (GET/Returns) and resource (order details by web order number), plus the underlying endpoint. It doesn't distinguish itself from sibling lookups like get_orderhistory_salesordernumber or get_order_by_ordernumber, leaving the agent to infer which identifier type to use.

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 exclusions. The description never says to prefer get_orderhistory_salesordernumber when the user has a sales order number instead of a web order number, even though that is the key routing decision among the visible siblings.

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