Skip to main content
Glama

create_inbound_plan

ACTION. Crea un PIANO di spedizione FBA ("Send to Amazon", Fulfillment Inbound v2024-03-20): SKU + quantità + indirizzo di ORIGINE (magazzino/fornitore del seller). È il PASSO 1 del flusso: il piano nasce come bozza modificabile, NON parte nessuna spedizione. SEQUENZA COMPLETA (guida l'utente passo-passo): 1) create_inbound_plan → 2) generate_inbound_options kind:"packing" → 3) confirm_inbound_option kind:"packing" → 4) set_packing_information (scatole) → 5) generate_inbound_options kind:"placement" (split + FEE da mostrare all'utente) → 6) confirm_inbound_option kind:"placement" = spedizioni CREATE. Trasporto/etichette/ritiro si completano poi in Seller Central (questa versione non li copre). PRIMA di chiamare: mostra all'utente il riepilogo (SKU, quantità, indirizzo) e chiedi conferma esplicita. Ripensamenti: cancel_inbound_plan.

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": {
      "items": "<items>",
      "source_address": "<source_address>"
    },
    "name": "create_inbound_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNome del piano (max 40 char, opzionale)
itemsYesProdotti: array di { sku, quantity, ... }.
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.
source_addressYesIndirizzo di origine della merce

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changed
    • addedInput schema / properties / items / description
      Added value: +"Prodotti: array di { sku, quantity, ... }."
    • addedInput schema / properties / items / items / properties / quantity / description
      Added value: +"Quantità in unità (intero >= 0)."
    • addedInput schema / properties / items / items / properties / sku / description
      Added value: +"SKU del venditore, esattamente come in Seller Central (maiuscole e minuscole contano)."
    • addedInput schema / properties / source_address / properties / address_line_1 / description
      Added value: +"Indirizzo del mittente, riga 1."
    • addedInput schema / properties / source_address / properties / address_line_2 / description
      Added value: +"Indirizzo del mittente, riga 2 (facoltativa)."
    • addedInput schema / properties / source_address / properties / city / description
      Added value: +"Città."
    • addedInput schema / properties / source_address / properties / company_name / description
      Added value: +"Ragione sociale del mittente."
    • addedInput schema / properties / source_address / properties / email / description
      Added value: +"Indirizzo email."
    • addedInput schema / properties / source_address / properties / name / description
      Added value: +"Nome del piano inbound, visibile in Seller Central."
    • addedInput schema / properties / source_address / properties / phone_number / description
      Added value: +"Telefono in formato internazionale, es. +390612345678."
    • addedInput schema / properties / source_address / properties / postal_code / description
      Added value: +"CAP."
    • addedInput schema / properties / source_address / properties / state_or_province_code / description
      Added value: +"Sigla provincia o stato, es. LT."
  2. Changed1 schema field changed
    • addedInput schema / properties / items / items / properties / manufacturing_lot_code
      Added value: +{
      +  "description": "Lotto di produzione (se richiesto)",
      +  "type": "string"
      +}
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false; the description adds the crucial behavioral fact that the plan is born as an editable draft and that 'NON parte nessuna spedizione'. It also imposes a pre-call confirmation ritual (show summary, ask explicit consent). It stops short of disclosing permission requirements or failure modes, so it is strong but not exhaustive.

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 action and resource, then organized into a numbered sequence that is easy to scan. It is dense and long, but nearly every sentence carries routing or safety information; the only slightly expendable part is the recap of the full downstream sequence inside a creation tool.

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 nested-object, 5-parameter creation tool with no output schema, the description covers what is created, what is deliberately not created, the surrounding workflow, the pre-call confirmation step, and the reversal path. Nothing an agent needs to invoke it correctly is missing.

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 every parameter (including the nested items and source_address fields) is already documented in structured form. The description only restates the item triple (SKU, quantità, indirizzo) without adding format or constraint detail beyond the schema. Baseline 3 is correct.

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 'ACTION. Crea un PIANO di spedizione FBA' and names the exact API surface (Send to Amazon, Fulfillment Inbound v2024-03-20), then enumerates the inputs it consumes (SKU + quantità + indirizzo di origine). It is immediately distinguishable from siblings like get_inbound_plan or generate_inbound_options.

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 positions itself as 'PASSO 1' of a six-step sequence, naming each subsequent sibling tool in order (generate_inbound_options, confirm_inbound_option, set_packing_information). It also states the boundary (transport/labels/ritiro are done in Seller Central and are not covered here) and routes second thoughts to cancel_inbound_plan.

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