Skip to main content
Glama
Sign In
mouser-mcp

mouser-mcp

by bradford-tech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get Mouser order options

get_order_options
Read-onlyIdempotent

Retrieves available shipping methods, payment methods, addresses, tax certificates, and VAT accounts for a Mouser cart so you can preview an order.

Instructions

Shipping methods, payment methods, addresses, tax certificates and VAT accounts available for ordering a Mouser cart. Use the returned values when previewing an order.

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": {
      "cartKey": "<cartKey>"
    },
    "name": "get_order_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
cartKeyYes
currencyCodeNoe.g. USD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.5

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds that the result is a set of selectable ordering options tied to a cart, but says nothing about authorization requirements, whether results vary by account, or what an empty/missing cart yields.

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 with the content list front-loaded and the usage note trailing. Nothing is redundant, though the opening is a bare noun phrase rather than a direct statement of the action.

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?

With no output schema, the description does useful work by enumerating the categories returned. It still omits the result shape (IDs vs. objects), whether options are filtered by country/account, and the login/auth requirements, which matter for a live supplier API call.

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%: currencyCode has only a terse 'e.g. USD' and cartKey has no description at all. The description's phrase 'for ordering a Mouser cart' weakly clarifies that cartKey identifies the cart, but it adds no detail on currencyCode or on the effect of currency on the returned options.

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 the concrete resources returned (shipping methods, payment methods, addresses, tax certificates, VAT accounts) for a Mouser cart, which is specific enough for an agent to know what it retrieves. It lacks an explicit verb and never distinguishes itself from siblings like get_cart or get_order, so an agent must infer that this is the pre-order options lookup.

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?

'Use the returned values when previewing an order' implies the downstream use, which gives some context for when to call it. There is no statement of prerequisites, no when-not guidance, and no mention of alternatives among the 13 sibling tools.

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