Skip to main content
Glama
Sign In
mouser-mcp

mouser-mcp

by bradford-tech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get a Mouser order

get_order
Read-onlyIdempotent

Retrieve details for a single Mouser order—line items, status, shipping, and payment—by order number.

Instructions

Details of one Mouser order: lines, status, shipping and payment.

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

Input Schema

NameRequiredDescriptionDefault
orderNumberYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.5

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful context by enumerating what the response contains (lines, status, shipping, payment), but says nothing about authorization requirements, openWorld behavior, or what happens for an unknown order number.

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?

A single front-loaded sentence fragment with zero filler and the returned fields grouped efficiently. It reads as a label rather than a full sentence, but nothing 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, single-parameter tool with no output schema, knowing the returned facets is mostly sufficient. The missing pieces are the source/format of orderNumber and error behavior for nonexistent orders, which the description leaves entirely uncovered.

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 description coverage is 0% for the single orderNumber parameter, so the description carries the burden but only implies a unique identifier via 'one Mouser order.' It does not state the expected format, where the order number comes from (e.g., get_order_history or create_cart_from_order), or what counts as valid.

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 names a specific resource and scope: one Mouser order, with the returned facets (lines, status, shipping, payment). That is clearly a single-order detail lookup rather than a list, which separates it from get_order_history, though the description never names those siblings explicitly.

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 statement and no mention of alternatives, even though siblings like get_order_history and get_order_options overlap in topic. An agent must infer that this is the single-order lookup by the phrase 'one Mouser order' alone.

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

Deploy Server

Other Tools