Skip to main content
Glama
Mouser MCP

Mouser MCP

by RainnWorks

get_cart

Read-only

Fetches a Mouser cart by cart key, letting clients review line items, quantities, and pricing before checkout or order placement.

Instructions

[MouserCart] GET /api/v{version}/cart Returns the cart

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

Input Schema

NameRequiredDescriptionDefault
cartKeyYes
versionNoAPI version. Defaults to 1.1
countryCodeNoOptional. If not provided, the billing/shipping address associated with the account will be used to determine country code. If provided, country code will be used to determine shipping rules.
currencyCodeNoOptional. If not provided, the default currency code based on the billing/shipping address associated with the account will be used to determine currency code. If provided, currency code will be used to price the cart.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/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, but the description adds nothing beyond that: no note on whether an invalid/empty cartKey errors, whether currency/country affect returned pricing, or what the response contains. For a read tool with no output schema, this leaves the agent with little behavioral context.

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 brief and front-loads the resource, but the raw endpoint path '/api/v{version}/cart' largely duplicates structured schema information and the second line 'Returns the cart' is near-tautological. The wording is not wasteful in length, but the content it spends words on adds little.

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?

For a four-parameter tool with no output schema and a required cartKey, the description omits what is returned (line items, totals, pricing affected by country/currency), error behavior for unknown keys, and authentication expectations. It is far too thin to let an agent call and interpret the result confidently.

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 75%, so much of the parameter meaning is already structured (countryCode and currencyCode have descriptions), but the required cartKey has no schema description and the tool description does not explain it at all. The description adds zero parameter meaning beyond the bare path template, so it does not compensate for the undocumented required key.

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 identifies the operation as a GET of the cart resource via the endpoint path and 'Returns the cart', so an agent knows it is a read of a cart. However, 'Returns the cart' is close to a restatement of the name, and it gives no scope detail (whose cart, keyed how, what it contains) to distinguish it from siblings like post_cart or the order-retrieval tools.

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 at all: no mention of when to call this versus post_cart (which likely creates/updates the cart) or the order-history endpoints. The only implied usage is that it retrieves a cart, which the name already conveys.

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