Skip to main content
Glama
Mouser MCP

Mouser MCP

by RainnWorks

get_orderhistory_salesordernumber

Read-only

Retrieve complete details for a specific Mouser sales order number, including line items and status, to review purchase history and verify past transactions.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
versionNoAPI version. Defaults to 1.1
salesOrderNumberYes

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. Beyond that, the description says only that it 'returns order details' — nothing about what happens on an unknown order number, credentials/API-key requirements, or result cardinality. It carries no behavioral context the agent cannot already infer from name plus annotations.

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, front-loaded sentences with no filler; the functional statement comes first. Minor waste is the repeated bracket tag and raw HTTP path, which duplicate information already in the tool name.

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?

With no output schema, the description should explain what 'order details' contains (line items, status, totals) and any not-found behavior. It instead leaves the return value and edge cases entirely undefined for a tool whose only purpose is retrieval.

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%: the `version` parameter is documented in the schema with its default, but `salesOrderNumber` has no schema description. The description merely restates 'for the supplied sales order number' without giving format, examples, or whether it is numeric or alphanumeric, so it fails to compensate for the 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?

States a specific verb and resource ('Returns order details') scoped to a 'sales order number', which inherently distinguishes it from date-filter and web-order-number siblings. The added HTTP path prefix '[MouserOrderHistory] GET /api/v{version}/orderhistory/salesOrderNumber' is redundant noise rather than differentiation.

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?

Usage is only implied: the agent must infer it should call this when it has a sales order number rather than a web order number or date range. No explicit when-to-use, when-not-to-use, or named alternative is given, even though get_orderhistory_webordernumber and get_orderhistory_bydaterange are obvious confusables.

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