Skip to main content
Glama

Nova Amazon MCP Server

set_stock_defaults

Destructive

Set ONE account's numbers of the TOP table of the Supply chain page — the warehouse & 3PL setup: per warehouse (its stock region, or its name as get_setup domain=supply_chain lists it) the transit to Amazon, the target stock at Amazon, the target stock at the warehouse and the transit from the factory; per account (region 'ALL') the production lead time; and the factory lines (goods straight from a country to a territory). These are ranks 3 and 4 of the ladder, above the fleet default (rank 5, Nova's number, the page's gold figure) and below the product's own lines (import_supply_chain): a value set here reaches every product without its own number. Fields you omit keep their current value, null clears one; when a line's numbers end up blank its row is deleted. Give ONE region at the top level (the form of before 2026-10-22), or rows (several regions or warehouses at once) and / or factoryLines. TWO-STEP: call WITHOUT commit to preview current → new per parameter, show the user, then commit with the confirmationToken. Requires the OAuth connection and the OWNER role.

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": {
      "account": "<account>"
    },
    "name": "set_stock_defaults"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsNoSeveral lines of the top table at once: one per region or warehouse, with the fields to change.
commitNoOmit/false = preview (no write). true = write; requires the confirmationToken from the preview.
reasonNoOne sentence, ALWAYS IN ENGLISH (regardless of the conversation language), on WHY you are making this call — the user question or your analytical goal. Recorded so the seller can see how their data is used.
regionNoA stock region as get_setup domain=stock lists them ('USA', 'EU_FBA', 'UK', 'Canada'…; 'US', 'EU', 'GB' are accepted) or 'ALL' (every region without its own row).
accountYesThe seller account (seller_partner_id, or an unambiguous account name).
factoryLinesNoThe factory lines of the top table: one per (country, territory), with the fields to change.
targetDaysAmazonNoDays of cover to hold at Amazon (FBA + AWD). Omit = unchanged, null = clear.
confirmationTokenNoThe token the preview returned.
targetDaysExternalNoDays of cover to hold at the external location; 0 for sellers shipping straight to FBA. Omit = unchanged, null = clear.
leadTimeTransitDaysNoDays in transit to the external location or to Amazon. Omit = unchanged, null = clear.
leadTimeProductionDaysNoDays from the purchase order to the goods leaving the factory. Omit = unchanged, null = clear.
leadTimeToWarehouseDaysNoDays from the factory to the warehouse / 3PL; 0 when the goods ship straight to Amazon. Omit = unchanged, null = clear.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / factoryLines / items / properties / region / description
      Previous value: -"A stock region as get_stock_setup lists them ('USA', 'EU_FBA', 'UK', 'Canada'…; 'US', 'EU', 'GB' are accepted). Never 'ALL': the units sit in one place."New value: +"A stock region as get_setup domain=stock lists them ('USA', 'EU_FBA', 'UK', 'Canada'…; 'US', 'EU', 'GB' are accepted). Never 'ALL': the units sit in one place."
    • changedInput schema / properties / region / description
      Previous value: -"A stock region as get_stock_setup lists them ('USA', 'EU_FBA', 'UK', 'Canada'…; 'US', 'EU', 'GB' are accepted) or 'ALL' (every region without its own row)."New value: +"A stock region as get_setup domain=stock lists them ('USA', 'EU_FBA', 'UK', 'Canada'…; 'US', 'EU', 'GB' are accepted) or 'ALL' (every region without its own row)."
    • changedInput schema / properties / rows / items / properties / warehouse / description
      Previous value: -"The warehouse as get_supply_chain_setup names it: its region takes the numbers."New value: +"The warehouse as get_setup domain=supply_chain names it: its region takes the numbers."
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations declare a destructive write, and the description substantiates that with concrete consequences beyond them: omitted fields keep their value, null clears one, and a line whose numbers all become blank has its row deleted. It additionally discloses the preview/commit protocol with confirmationToken and the OAuth/OWNER authorization requirement.

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?

Information-dense with little pure waste, but it is delivered as one long run-on block mixing hierarchy, deletion semantics, call shape, and auth, so key operational facts (two-step commit, permissions) are buried rather than front-loaded. Bullet-style separation would materially improve scanability.

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

Completeness5/5

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

For a 12-parameter destructive mutation with no output schema, the description covers everything an agent needs: precedence against the fleet default and product lines, per-line deletion behavior, the preview-then-commit flow, both input shapes, and the required role. Nothing material is left to inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so a 3 is the floor, but the description adds real semantics: how `warehouse` resolves to a region ('its region takes the numbers'), that region 'ALL' means per-account level, that factoryLines require a country/territory pair and never 'ALL', and the legacy single-region form versus `rows`. This meaningfully exceeds the per-field 'Omit = unchanged, null = clear' boilerplate in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: it sets one account's Supply-chain top-table numbers, enumerating exactly which figures (warehouse transit, target stock at Amazon/warehouse, production lead time, factory lines). It also positions the tool in a precedence ladder and names the sibling that covers the product-level case, import_supply_chain, so the agent can tell them apart without reading either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit guidance on when values set here apply ('a value set here reaches every product without its own number') versus when to use import_supply_chain for product-specific lines, plus the rank relationship to the rank-5 fleet default. It also spells out the mandatory two-step flow, the alternative input shapes (single `region` vs `rows`/`factoryLines`), and the OWNER-role prerequisite.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.