Skip to main content
Glama
Mouser MCP

Mouser MCP

by RainnWorks

get_order_by_ordernumber

Read-only

Retrieve full order details by supplying a Mouser web order number, including status, items, and pricing, so you can verify or review a specific order.

Instructions

[Order] GET /api/v{version}/order/{orderNumber} 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": {
      "orderNumber": "<orderNumber>"
    },
    "name": "get_order_by_ordernumber"
  }
}

Input Schema

NameRequiredDescriptionDefault
versionNoAPI version. Defaults to 1.1
orderNumberYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered externally. The description adds useful context by disclosing the underlying GET route and clarifying that the identifier is a web order number, but says nothing about not-found behavior, auth requirements, or response shape.

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 outcome front-loaded after a bracketed category tag. The raw route template is mildly redundant but does convey versioning, and nothing else is wasted.

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 definition covers the essentials of what it fetches. It stops short of describing what 'order details' contains, which matters since no output schema exists to fill that gap.

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%: version is documented inline while orderNumber is bare. The description partially compensates by identifying orderNumber as a web order number (as opposed to a sales order number), but adds no format, range, or example for an int32 identifier.

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 ('Returns order details') plus a disambiguating scope: the lookup is by *web* order number, which separates it from a sales-order-number lookup. It does not name a sibling outright, so it falls short of 5.

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?

The description says what the tool does but never says when to prefer it over the sibling history/lookup tools (e.g. get_orderhistory_webordernumber) or what preconditions apply. Usage is only implied by the resource name.

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