Skip to main content
Glama
Mouser MCP

Mouser MCP

by RainnWorks

get_orderhistory_bydaterange

Read-only

Retrieve Mouser order history for a specified date range to review past purchases and track orders within that period.

Instructions

[MouserOrderHistory] GET /api/v{version}/orderhistory/ByDateRange Returns Order History by date range

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": {
      "startDate": "<startDate>",
      "endDate": "<endDate>"
    },
    "name": "get_orderhistory_bydaterange"
  }
}

Input Schema

NameRequiredDescriptionDefault
endDateYese.g. 4/30/2019 (mm/dd/yyyy)
versionNoAPI version. Defaults to 1.1
startDateYese.g. 1/30/2019 (mm/dd/yyyy)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/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 the safety profile is covered and the bar is lower. Beyond that, the description adds nothing: it does not say whether the range is inclusive, how results are ordered, whether pagination applies, or what volume of data to expect.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loaded, but the second clause merely re-serializes the tool name and the bracketed API route is operational noise for an agent rather than discriminating information. Nothing is verbose, yet little of the text earns its place.

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?

This is a simple read-only retrieval tool with fully documented required parameters and no output schema, so the description does not need to explain return values. Still, the unresolved overlap with the bydatefilter sibling and the absence of any range-semantics detail leave a meaningful gap for an agent choosing between two near-identical history endpoints.

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 description coverage is 100% and both required date parameters carry format examples (mm/dd/yyyy), so the schema does the heavy lifting and the baseline of 3 applies. The description adds no extra meaning about how startDate and endDate bound the query or how the defaulted version parameter affects behavior.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a verb and resource ('Returns Order History by date range') and echoes the endpoint path, so the basic purpose is recoverable. However, it is essentially a restatement of the tool name and route, and it offers nothing to distinguish this from the sibling get_orderhistory_bydatefilter, which an agent would plausibly confuse it with.

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, no indication of which scenario selects this over get_orderhistory_bydatefilter or the salesorder/webordernumber variants, and no prerequisites or rate-limit context. The agent must infer the routing decision entirely from the names.

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