Skip to main content
Glama

get_inbound_plan

Read-only

READ-ONLY. Dettaglio di UN piano inbound FBA v2024 (stato, indirizzo origine, righe SKU con quantità/prep/label). Con operation_id (invece di inbound_plan_id) fa il polling di un'operazione asincrona pendente (create/generate/confirm) e ne ritorna stato + problemi. Per l'ELENCO dei piani usa get_inbound_plans.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_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.
operation_idNoAlternativa: polla lo stato di un'operazione async
inbound_plan_idNoId 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

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds real behavioral context beyond them: the polling semantics for pending async operations (create/generate/confirm) and what that mode returns (stato + problemi). It does not cover error behavior when neither identifier is supplied, which keeps it off a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three dense sentences, front-loaded with the READ-ONLY marker, then the detail payload, then the alternate mode, then the sibling pointer. No filler and nothing repeated without purpose.

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?

With no output schema, the description appropriately names the fields returned in both modes. The only gap is how errors or missing identifiers are handled in a tool where nothing is required, preventing a perfect score. For a two-mode read tool it is otherwise sufficient to invoke correctly.

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; the description earns an extra point by explaining the either/or relationship between operation_id and inbound_plan_id and by enumerating which async operation types can be polled, which the schema text only gestures at. account_id semantics are left entirely to the schema, which is acceptable given full coverage.

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?

States a specific verb and resource ('Dettaglio di UN piano inbound FBA v2024') and immediately scopes what the detail contains (stato, indirizzo origine, righe SKU con quantità/prep/label). It also carves out the second mode (operation_id polling) and names the sibling get_inbound_plans for listing, so an agent can distinguish it from siblings without opening a 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?

Explicit routing is given in both directions: 'Per l'ELENCO dei piani usa get_inbound_plans' covers when NOT to use this tool, and 'Con operation_id (invece di inbound_plan_id)' tells the agent which of the two identifiers selects which mode. That resolves the ambiguity created by zero required parameters.

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