Skip to main content
Glama
Mouser MCP

Mouser MCP

by RainnWorks

get_order_currencies

Read-only

Retrieve available order currencies using the account billing address and default or provided shipping country to determine valid currency options for an order.

Instructions

[Order] GET /api/v{version}/order/currencies Returns a list of available currencies based on the billing address and default shipping address associated with the account.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_order_currencies"
  }
}

Input Schema

NameRequiredDescriptionDefault
versionNoAPI version. Defaults to 1.1
shippingCountryCodeNoOptional. If not provided, the default shipping address associated with the account will be used to determine currency results.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/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. The description earns credit beyond that by disclosing a non-obvious implicit dependency — results are derived from the account's billing address and default shipping address — which tells the agent the same call can return different sets per account. It does not cover caching or ordering of results, which is minor for a lookup.

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 compact sentences with the resource statement front-loaded and no filler. The leading route template '[Order] GET /api/v{version}/order/currencies' is somewhat redundant with the schema's version parameter but serves as an endpoint anchor.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-required-parameter read lookup with full schema coverage and no output schema, the definition supplies what an agent needs: what is returned and what the result depends on. The absence of any note on response shape or currency code format is a small gap but not blocking.

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%, so both version and shippingCountryCode are already documented in the schema, including the optional/default-shipping fallback. The description's mention of default shipping address reinforces but does not extend that meaning, so the baseline of 3 applies.

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 states a specific verb and resource — 'Returns a list of available currencies' — and adds the resolution basis (billing address plus default shipping address). The resource is distinct from the nearest sibling (get_order_countries), but the definition never names that sibling, so differentiation is implicit rather than explicit.

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: an agent can infer this is the read path for currency options during order creation, but there is no statement of when to prefer it over other lookups or any preconditions. No exclusions or alternatives are given.

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