Skip to main content
Glama

Nova Amazon MCP Server

import_fbm_zone_rates

Destructive

Import the seller's FBM RATE BOOK for ONE account — the rates the P&L applies to merchant-fulfilled orders: 'shipping' per container ('EU_REGION', 'NA_REGION', 'FE_REGION': one rate for every country of it without a rate of its own), per delivery country ('DE', 'FR'…) or 'ROW' (every other country), and the handling costs 'packing' (per parcel) and 'picking' (per unit) on a container or on 'ALL'. This is the FIRST thing to set up: nothing is priced until a zone rate exists. TWO-STEP, never skip the preview: call WITHOUT commit; the server validates and returns per-line warnings, a diff (one line per zone|kind) and a confirmationToken; show them to the user and only after explicit approval call again with the SAME account/mode/rows plus commit:true and the token. Mode 'merge' (default) adds or updates only the (zone, kind, period) lines you send; 'replace' restates the WHOLE rate book — every line absent from rows is deleted. 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>",
      "rows": "<rows>"
    },
    "name": "import_fbm_zone_rates"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNo'merge' (default): only the sent lines change. 'replace': the rows are the entire rate book.
rowsYes
commitNoOmit/false = preview (validate + diff, 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.
accountYesThe seller account (seller_partner_id, or an unambiguous account name). One account per call.
confirmationTokenNoThe token the preview returned — proves the user saw exactly this payload.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, and the description goes beyond them by disclosing that 'replace' deletes every line absent from rows, that the preview returns per-line warnings, a diff and a confirmationToken, and that the token must accompany the commit call with the identical payload. It stops short of describing persistence behavior (e.g., what a partial failure implies), but the destructive surface is clearly disclosed.

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?

Front-loaded with the resource and scope, then the setup priority, then the workflow, then mode semantics and prerequisites — a logical order with no filler sentences. The zone enumeration is dense and partly duplicated later in the two-step paragraph, which slightly hurts scanability but each block earns its place.

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 destructive, two-step import with no output schema, the description covers the prerequisite auth/role, the preview/commit contract, the token requirement, the mode semantics and the scope constraint (one account per call). An agent has everything needed to invoke it without a failed first attempt.

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

Parameters4/5

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

Schema coverage is already 83%, so the schema does most of the work, but the description adds real meaning: the enumerations of zone containers ('EU_REGION' covers every country without its own rate), the 'ROW' fallback, 'ALL' being valid only for packing/picking, and the default semantics of 'mode'. It largely restates the schema's zone and currency text, which caps it below 5.

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 ('Import the seller's FBM RATE BOOK for ONE account') and enumerates exactly what the rate book contains: shipping per container/country/ROW plus packing and picking handling costs. An agent can distinguish this from import_fbm_costs or import_cogs without opening any 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?

Explicitly says this is 'the FIRST thing to set up: nothing is priced until a zone rate exists', describes the mandatory two-step preview-then-commit flow with the approval gate, and spells out when 'merge' vs 'replace' applies. Prerequisites (OAuth connection, OWNER role) are named, leaving no inference.

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.