Skip to main content
Glama

update_mfn_quantity

Destructive

Update MFN inventory quantity for a SKU

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": {
      "sku": "<sku>",
      "quantity": "<quantity>"
    },
    "name": "update_mfn_quantity"
  }
}

Input Schema

NameRequiredDescriptionDefault
skuYesSKU del venditore, esattamente come in Seller Central (maiuscole e minuscole contano).
quantityYesQuantità in unità (intero >= 0).
account_idNoID dell'outpost Amazon (= un seller su uno specifico marketplace; vedi list_clients). Opzionale se il token è legato a un solo outpost.
confirm_idNoToken di conferma ritornato dall'anteprima. Ripassa lo STESSO payload + confirm_id per eseguire davvero la scrittura.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / quantity / description
      Added value: +"Quantità in unità (intero >= 0)."
    • addedInput schema / properties / sku / description
      Added value: +"SKU del venditore, esattamente come in Seller Central (maiuscole e minuscole contano)."
  2. First observed

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true and openWorldHint=true, so the safety profile is known; the description adds nothing on top of that. It does not say that the quantity is overwritten rather than incremented, nor that the write actually executes only on a second call carrying confirm_id, which is the most consequential behavior for a destructive operation.

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?

The single sentence is front-loaded and free of waste, but at seven words it is undersized for a destructive write tool with a confirmation-token workflow. Conciseness is achieved by omission here rather than by tight editing.

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 destructive, open-world mutation with four parameters and no output schema, the description omits the preview/confirm execution model, the Amazon MFN/FBM framing, and what happens to quantity on failure or concurrency. Much of this is recoverable from the rich schema, but the description itself leaves the agent to assemble the workflow.

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 coverage is 100% and each parameter carries its own description, including the confirm_id two-step flow and the account_id fallback, so the schema does the explanatory work. The description contributes no additional meaning about how sku casing or the integer quantity constraint is enforced, making the baseline 3 appropriate.

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 names a specific verb (Update) and resource (MFN inventory quantity) scoped to a single SKU, which is concrete enough for an agent to know what changes. It does not, however, distinguish itself from siblings like bulk_update_inventory or woo_update_stock, so the agent must infer that this is the single-SKU, Amazon-MFN variant.

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, no mention that this is the single-SKU counterpart to bulk_update_inventory, and no stated prerequisites such as account scoping or the preview-then-confirm requirement. The agent gets a purpose but no routing logic.

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.

Resources