Skip to main content
Glama

confirm_inbound_option

Destructive

ACTION. Conferma un'opzione del piano inbound FBA scelta dall'utente. kind:"packing" + packing_option_id = fissa l'imballo (poi servono le scatole: set_packing_information). kind:"placement" + placement_option_id = IMPEGNO VERO: le spedizioni vengono CREATE con lo split e le fee di quell'opzione (ritorna gli shipment_ids). Conferma SOLO dopo che l'utente ha visto fee e split e ha approvato esplicitamente. Trasporto/etichette si completano in Seller Central.

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": {
      "inbound_plan_id": "<inbound_plan_id>",
      "kind": "<kind>",
      "option_id": "<option_id>"
    },
    "name": "confirm_inbound_option"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesFase del piano inbound: packing oppure placement.
option_idYespacking_option_id o placement_option_id (da generate_inbound_options)
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.
inbound_plan_idYesId del piano inbound FBA (da get_inbound_plans).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / inbound_plan_id / description
      Added value: +"Id del piano inbound FBA (da get_inbound_plans)."
    • addedInput schema / properties / kind / description
      Added value: +"Fase del piano inbound: packing oppure placement."
  2. First observed

TDQS

A4.3/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, but the description adds the crucial consequence: with kind:"placement" real shipments are CREATED with that option's split and fees, and it returns shipment_ids. It also notes that transport/labels are finished in Seller Central. It stops short of saying whether created shipments can be undone, which matters for a destructive action.

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?

Dense but front-loaded: the action, the two mode branches, the approval precondition and the hand-off all appear in a few tight sentences with no filler. Minor redundancy with schema text on the option IDs keeps it from a 5.

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?

No output schema exists, and the description compensates by naming the return (shipment_ids) and the downstream steps. The two-step confirm_id/preview flow is left to the schema, which documents it fully, so the remaining gap is small for a destructive 5-parameter tool.

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 the schema already documents kind, option_id, account_id, confirm_id and inbound_plan_id. The description reinforces the kind→option-id pairing and the origin of the IDs (generate_inbound_options, get_inbound_plans), but adds little that the schema does not already state, so the baseline 3 applies.

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?

Opens with an explicit action marker and a concrete verb+resource ('Conferma un'opzione del piano inbound FBA'), then splits the behavior into two named modes (kind:"packing" vs kind:"placement"), making clear this is the write/commit counterpart to the option-generating siblings rather than a read.

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?

Gives an explicit precondition ('Conferma SOLO dopo che l'utente ha visto fee e split e ha approvato esplicitamente'), states what each mode leads to, and routes the packing path onward to set_packing_information for boxes. An agent knows both when to call it and what must happen before calling it.

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