Skip to main content
Glama

cancel_inbound_plan

Destructive

ACTION. Annulla un piano inbound FBA v2024 non ancora spedito (torna VOIDED). Usalo per i ripensamenti su un piano creato per errore o non più necessario. Chiedi conferma esplicita all'utente prima di chiamare.

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

Input Schema

NameRequiredDescriptionDefault
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. Changed1 schema field changed
    • addedInput schema / properties / inbound_plan_id / description
      Added value: +"Id del piano inbound FBA (da get_inbound_plans)."
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds genuinely useful context: the terminal state becomes VOIDED, the plan must not have shipped, and the agent must obtain explicit user confirmation first. It omits, however, that a confirm_id/preview round-trip is required before the write actually executes, and does not say whether the change is reversible.

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?

Three short sentences, front-loaded with the action and the resulting state, then usage, then the confirmation rule. Little waste; the 'ACTION.' prefix is mild boilerplate but signals a mutation clearly.

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 destructive one-required-param tool with annotations covering safety and no output schema, this covers what the agent needs: eligibility, resulting state, and the confirmation gate. The two-phase preview/confirm mechanics live only in the schema, which is an acceptable but notable handoff.

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 all three parameters are documented in the schema, including the confirm_id two-step write flow. The description adds only the eligibility constraint on inbound_plan_id, so baseline 3 applies.

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?

Names a specific verb (cancel) and resource (FBA inbound plan v2024), plus the resulting state (VOIDED) and a precondition (not yet shipped). It is clearly distinguishable from get/create siblings, though it never names a sibling explicitly to route away from.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

States when to use it ('ripensamenti su un piano creato per errore o non più necessario') and gives a procedural rule (ask the user for explicit confirmation). It implies a when-not via the 'non ancora spedito' precondition but never states what to do instead for an already-shipped 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