Skip to main content
Glama

generate_inbound_options

ACTION (bozze non vincolanti). Genera E elenca in una sola chiamata le opzioni del piano inbound FBA: kind:"packing" = opzioni di imballo (packing groups); kind:"placement" = opzioni di DESTINAZIONE con split tra centri Amazon e FEE per opzione (inbound placement fee vs Amazon-optimized) — mostra SEMPRE fee e numero spedizioni di ogni opzione all'utente prima di confermare. Richiede il piano creato (create_inbound_plan); placement richiede packing confermato + scatole inviate (set_packing_information). Se esistono GIÀ opzioni per quel kind le ri-elenca SENZA rigenerarle (regenerate:true per forzare una nuova generazione, es. dopo aver cambiato il piano). Se torna IN_PROGRESS: verifica con get_inbound_plan (operation_id) e poi richiama — NON rigenerare alla cieca.

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>"
    },
    "name": "generate_inbound_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesFase del piano inbound: packing oppure placement.
account_idNoID dell'outpost Amazon (= un seller su uno specifico marketplace; vedi list_clients). Opzionale se il token è legato a un solo outpost.
regenerateNotrue = forza una NUOVA generazione anche se esistono già opzioni
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.7/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false and destructiveHint=false; the description adds substantially more: the output is a non-binding draft ("bozze non vincolanti"), the call is effectively idempotent unless regenerate is set, and it can return an IN_PROGRESS async state that must be polled via get_inbound_plan. It also imposes a workflow obligation (always show fees and shipment counts to the user before confirming). No contradiction with annotations — a generator is correctly flagged as a write operation, and non-binding drafts are consistent with destructiveHint=false.

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?

Every sentence carries operational content — prerequisites, idempotency, async handling, and the user-confirmation requirement — and the two kind values are front-loaded. It is dense and caps-heavy but not padded; minor deduction for readability of the run-on mid-section.

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?

For a tool with prerequisites, an async IN_PROGRESS path, and no output schema, the description covers the return shape well enough (options plus fee and shipment count per option for placement). Packing-mode return content is only sketched as "packing groups," leaving a small gap, but nothing needed to invoke the tool correctly is missing.

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 100%, so the baseline is 3, but the description goes further by explaining what each kind actually yields (packing groups vs. placement splits with inbound placement fee vs. Amazon-optimized) and by clarifying that regenerate:true forces a new generation when options already exist. It does not add anything about account_id beyond the schema's own note, so it stops short of 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?

The description opens with a specific verb+resource ("Genera E elenca in una sola chiamata le opzioni del piano inbound FBA") and then disambiguates the two operating modes: kind:"packing" = packing groups, kind:"placement" = destination options with Amazon center split and per-option fees. An agent can distinguish this from create_inbound_plan or get_inbound_plan 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?

It gives explicit prerequisites (create_inbound_plan first; placement additionally requires confirmed packing + boxes sent via set_packing_information), states the re-list-instead-of-regenerate default and the regenerate:true override, and routes the agent to get_inbound_plan when IN_PROGRESS comes back with an explicit "do NOT regenerate blindly" warning. This is when-to-use, when-not-to-use and named alternatives in one place.

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