Skip to main content
Glama
Mouser MCP

Mouser MCP

by RainnWorks

post_order_options_query

Destructive

Fetches available shipping methods, payment methods, tax certificates, VAT accounts, and saved credit cards for an account, using an optional cart key for accurate shipping rates.

Instructions

[Order] POST /api/v{version}/order/options/query Returns available shipping methods, payment methods, tax certificates, VAT accounts, and saved credit cards for the account.

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": {
      "request": "<request>"
    },
    "name": "post_order_options_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYes
versionNoAPI version. Defaults to 1.1

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

The description frames this purely as a returning/query operation ("Returns available shipping methods..."), yet the annotations declare readOnlyHint=false and destructiveHint=true, leaving the agent with two conflicting safety profiles and no explanation of why a query would be destructive. Beyond that, it discloses no auth requirements, rate limits, or whether any account state is touched, so the only real behavioral content is the list of returned data categories.

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 sentences, front-loaded, with the return enumeration doing the informative work and no padding. The raw route/version string is largely redundant with the tool name, but it is compact and does not obscure the payload.

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 and a deeply nested request object, listing the returned data categories is valuable and largely covers the response side. However, a tool flagged destructive whose description reads like a read query leaves a significant unanswered question about side effects and required entitlements, so the definition is adequate rather than complete.

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 50%, and the description adds nothing about the two top-level parameters — neither the required `request` wrapper nor `version` is mentioned, and the nested field behavior (CartKey influencing shipping accuracy, address defaults) exists only in the schema. The one genuinely useful semantic point, that results are scoped to the account, is implied but not tied to any parameter.

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?

"Returns available shipping methods, payment methods, tax certificates, VAT accounts, and saved credit cards for the account" names a specific resource (order options) and enumerates exactly what comes back, which clearly separates it from siblings like post_order or post_cart. The leading verb+route string ("[Order] POST /api/v{version}/order/options/query") is endpoint plumbing rather than added meaning, but the payload sentence carries the purpose.

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: the schema's OrderInializeRequestRoot/OrderInitialize naming hints this is the pre-checkout step that gathers shipping/payment options, but the description never states when to call it, what prerequisite state (cart/account) is needed, or how it relates to siblings such as post_order or get_cart. An agent can infer the checkout flow, but no explicit when/when-not guidance is given.

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